Re: [RFC PATCH 0/9] vhost-nvme: new qemu nvme backend using nvme target
From: Paolo Bonzini <pbonzini@redhat.com>
Date: 2015-11-25 19:32:36
Also in:
linux-nvme, qemu-devel
Possibly related (same subject, not in this thread)
- 2015-11-21 · Re: [RFC PATCH 0/9] vhost-nvme: new qemu nvme backend using nvme target · Paolo Bonzini <pbonzini@redhat.com>
- 2015-11-20 · [RFC PATCH 0/9] vhost-nvme: new qemu nvme backend using nvme target · mlin@kernel.org (Ming Lin)
- 2015-11-20 · Re: [RFC PATCH 0/9] vhost-nvme: new qemu nvme backend using nvme target · Christoph Hellwig <hch@lst.de>
- 2015-11-20 · [RFC PATCH 0/9] vhost-nvme: new qemu nvme backend using nvme target · mlin@kernel.org (Ming Lin)
On 25/11/2015 19:51, Ming Lin wrote:
quoted
Do you still have a blk_set_aio_context somewhere? I'm losing track of the changes.No.
You'll need it. That's what causes your error.
BTW, I'm not sure about qemu upstream policy. Do I need to first make the kernel side patch upstream? https://git.kernel.org/cgit/linux/kernel/git/mlin/linux.git/log/?h=nvme-google-ext
No problem, there's time. QEMU is in freeze right now, and the 2.6 cycle will last until March or so. Paolo