All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Changpeng Liu <changpeng.liu@intel.com>,
	qemu-devel@nongnu.org, stefanha@gmail.com,
	marcandre.lureau@redhat.com, felipe@nutanix.com,
	james.r.harris@intel.com
Subject: Re: [Qemu-devel] [PATCH v4 1/4] vhost-user: add new vhost user messages to support virtio config space
Date: Thu, 19 Oct 2017 20:43:19 +0300	[thread overview]
Message-ID: <20171019204305-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <42aa8736-bc23-d66d-27de-dbaf83ea2f99@redhat.com>

On Thu, Oct 19, 2017 at 05:43:18PM +0200, Paolo Bonzini wrote:
> On 19/10/2017 17:39, Michael S. Tsirkin wrote:
> >> Add VHOST_USER_GET_CONFIG/VHOST_USER_SET_CONFIG messages which can be
> >> used for live migration of vhost user devices, also vhost user devices
> >> can benefit from the messages to get/set virtio config space from/to the
> >> I/O target. For the purpose to support virtio config space change,
> >> VHOST_USER_SET_CONFIG_FD message is added as the event notifier
> >> in case virtio config space change in the I/O target.
> >>
> >> Signed-off-by: Changpeng Liu <changpeng.liu@intel.com>
> > I don't much like it that config is getting passed through.
> > 
> > IMO this makes managing things harder not easier.
> > 
> > How about specific messages about specific parts of
> > config space that you want to get from the backend?
> 
> In the case of virtio-blk that would be all of it.  Do you have a case
> in mind where some part of the configuration space is owned by QEMU?
> 
> Paolo

Yes. seg_max

  reply	other threads:[~2017-10-19 17:43 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19  5:24 [Qemu-devel] [PATCH v4 0/4] *** Introduce a new vhost-user-blk host device to Qemu *** Changpeng Liu
2017-10-19  5:24 ` [Qemu-devel] [PATCH v4 1/4] vhost-user: add new vhost user messages to support virtio config space Changpeng Liu
2017-10-19 11:37   ` Paolo Bonzini
2017-10-19 14:09   ` Stefan Hajnoczi
2017-10-19 15:36     ` Michael S. Tsirkin
2017-10-20 10:00       ` Stefan Hajnoczi
2017-10-23  4:47         ` Liu, Changpeng
2017-10-23 17:26           ` Stefan Hajnoczi
2017-10-24  0:52             ` Liu, Changpeng
2017-10-24 13:00               ` Stefan Hajnoczi
2017-10-19 15:39   ` Michael S. Tsirkin
2017-10-19 15:43     ` Paolo Bonzini
2017-10-19 17:43       ` Michael S. Tsirkin [this message]
2017-10-19 21:04         ` Paolo Bonzini
2017-10-20  0:27           ` Michael S. Tsirkin
2017-10-20  1:55             ` Liu, Changpeng
2017-10-20  2:12               ` Michael S. Tsirkin
2017-10-20  2:34                 ` Liu, Changpeng
2017-10-19  5:24 ` [Qemu-devel] [PATCH v4 2/4] vhost-user-blk: introduce a new vhost-user-blk host device Changpeng Liu
2017-10-19 11:33   ` Paolo Bonzini
2017-10-20  1:38     ` Liu, Changpeng
2017-10-19 15:17   ` Stefan Hajnoczi
2017-10-20  1:47     ` Liu, Changpeng
2017-10-20  9:54       ` Stefan Hajnoczi
2017-10-23  4:26         ` Liu, Changpeng
2017-10-23 12:55           ` Michael S. Tsirkin
2017-10-24  0:40             ` Liu, Changpeng
2017-10-23 17:11           ` Stefan Hajnoczi
2017-10-24  0:44             ` Liu, Changpeng
2017-10-24 12:53               ` Stefan Hajnoczi
2017-10-25  1:34                 ` Liu, Changpeng
2017-11-03 14:50                   ` Stefan Hajnoczi
2017-10-19  5:24 ` [Qemu-devel] [PATCH v4 3/4] contrib/libvhost-user: enable virtio config space messages Changpeng Liu
2017-10-19  5:24 ` [Qemu-devel] [PATCH v4 4/4] contrib/vhost-user-blk: introduce a vhost-user-blk sample application Changpeng Liu
2017-10-19 11:43   ` Paolo Bonzini
2017-10-20  1:39     ` Liu, Changpeng

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=20171019204305-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=changpeng.liu@intel.com \
    --cc=felipe@nutanix.com \
    --cc=james.r.harris@intel.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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.