diff options
| author | Xie Yongji <xieyongji@bytedance.com> | 2022-06-14 13:15:32 +0800 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2022-06-24 17:07:06 +0200 |
| commit | 779d82e1d305f2a9cbd7f48cf6555ad58145e04a (patch) | |
| tree | 39266452d6780f9435c04bb64a962104b1547f6b /qemu-io-cmds.c | |
| parent | 0862a087fd710a6c7ad4ea01d35309686e54e202 (diff) | |
| download | qemu-779d82e1d305f2a9cbd7f48cf6555ad58145e04a.zip qemu-779d82e1d305f2a9cbd7f48cf6555ad58145e04a.tar.gz qemu-779d82e1d305f2a9cbd7f48cf6555ad58145e04a.tar.bz2 | |
vduse-blk: Add name option
Currently we use 'id' option as the name of VDUSE device.
It's a bit confusing since we use one value for two different
purposes: the ID to identfy the export within QEMU (must be
distinct from any other exports in the same QEMU process, but
can overlap with names used by other processes), and the VDUSE
name to uniquely identify it on the host (must be distinct from
other VDUSE devices on the same host, but can overlap with other
export types like NBD in the same process). To make it clear,
this patch adds a separate 'name' option to specify the VDUSE
name for the vduse-blk export instead.
Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
Message-Id: <20220614051532.92-7-xieyongji@bytedance.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'qemu-io-cmds.c')
0 files changed, 0 insertions, 0 deletions