All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
	qemu-block@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	Karl Rister <krister@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/6] block: Add VFIO based driver for NVMe device
Date: Thu, 23 Feb 2017 19:19:42 +0800	[thread overview]
Message-ID: <20170223111942.GC14175@lemon.lan> (raw)
In-Reply-To: <a3f21946-e176-dbd2-3daf-49202e0bd85b@redhat.com>

On Thu, 02/23 11:50, Paolo Bonzini wrote:
> 
> 
> On 23/02/2017 11:48, Fam Zheng wrote:
> >>
> >> The first three patches add the driver, the others are to make qemu-img more
> >> efficient with the new driver.
> > Paolo, I wanted to also make ram_block_notifier_add notify existing ram blocks,
> > so that hot plugging of nvme:// will work as expected, but I don't know how to
> > write the code. Any suggestions? Or do you have a patch for that already?
> 
> I don't :) but it shouldn't be hard to do using qemu_ram_foreach_block:
> 
> typedef int (RAMBlockIterFunc)(const char *block_name, void *host_addr,
>     ram_addr_t offset, ram_addr_t length, void *opaque);
> 
> int qemu_ram_foreach_block(RAMBlockIterFunc func, void *opaque);
> 

Cool, I'll add that in v3.

Fam

      reply	other threads:[~2017-02-23 11:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23  9:18 [Qemu-devel] [PATCH v2 0/6] block: Add VFIO based driver for NVMe device Fam Zheng
2017-02-23  9:18 ` [Qemu-devel] [PATCH v2 1/6] nvme: Move NVMe definitions to a separate header Fam Zheng
2017-02-23  9:18 ` [Qemu-devel] [PATCH v2 2/6] stubs: Add stubs for ram block notifier API Fam Zheng
2017-02-23  9:49   ` Paolo Bonzini
2017-02-23  9:18 ` [Qemu-devel] [PATCH v2 3/6] block: Add VFIO based NVMe driver Fam Zheng
2017-02-23  9:43   ` Paolo Bonzini
2017-02-23 10:01     ` Fam Zheng
2017-02-23  9:18 ` [Qemu-devel] [PATCH v2 4/6] block: Introduce bdrv_dma_map and bdrv_dma_unmap Fam Zheng
2017-02-23  9:18 ` [Qemu-devel] [PATCH v2 5/6] block/nvme: Implement .bdrv_dma_map and .bdrv_dma_unmap Fam Zheng
2017-02-23  9:18 ` [Qemu-devel] [PATCH v2 6/6] qemu-img: dma map buffers Fam Zheng
2017-02-23  9:28 ` [Qemu-devel] [PATCH v2 0/6] block: Add VFIO based driver for NVMe device no-reply
2017-02-23 10:48 ` Fam Zheng
2017-02-23 10:50   ` Paolo Bonzini
2017-02-23 11:19     ` Fam Zheng [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170223111942.GC14175@lemon.lan \
    --to=famz@redhat.com \
    --cc=krister@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.