diff options
| author | Max Reitz | 2019-02-01 20:29:30 +0100 |
|---|---|---|
| committer | Max Reitz | 2019-02-25 15:11:27 +0100 |
| commit | cc61b0740f9b99942f18cc850eeffa302f4f328e (patch) | |
| tree | bcd43706b0079e26644ce3fb301113181105332a /include/exec | |
| parent | block: Do not copy exact_filename from format file (diff) | |
| download | qemu-cc61b0740f9b99942f18cc850eeffa302f4f328e.tar.gz qemu-cc61b0740f9b99942f18cc850eeffa302f4f328e.tar.xz qemu-cc61b0740f9b99942f18cc850eeffa302f4f328e.zip | |
block/nvme: Fix bdrv_refresh_filename()
Currently, nvme's bdrv_refresh_filename() is an exact copy of null's
implementation. However, for null, "null-co://" and "null-aio://" are
indeed valid filenames -- for nvme, they are not, as a device address is
still required.
The correct implementation should generate a filename of the form
"nvme://[PCI address]/[namespace]" (as the comment above
nvme_parse_filename() describes).
Signed-off-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Alberto Garcia <berto@igalia.com>
Message-id: 20190201192935.18394-27-mreitz@redhat.com
Signed-off-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'include/exec')
0 files changed, 0 insertions, 0 deletions