All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] Revert "vhost: rename VHOST_RESET_OWNER to VHOST_RESET_DEVICE"
Date: Wed, 21 Oct 2015 13:42:09 +0300	[thread overview]
Message-ID: <20151021134130-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20151021092140.GF3115@yliu-dev.sh.intel.com>

On Wed, Oct 21, 2015 at 05:21:40PM +0800, Yuanhan Liu wrote:
> On Wed, Oct 21, 2015 at 12:15:52PM +0300, Michael S. Tsirkin wrote:
> > On Wed, Oct 21, 2015 at 04:55:16PM +0800, Yuanhan Liu wrote:
> > > On Fri, Oct 16, 2015 at 10:47:49AM +0300, Michael S. Tsirkin wrote:
> > > > On Fri, Oct 16, 2015 at 03:32:56PM +0800, Yuanhan Liu wrote:
> > > > > On Fri, Oct 16, 2015 at 10:21:40AM +0300, Michael S. Tsirkin wrote:
> > > > > > On Fri, Oct 16, 2015 at 03:18:59PM +0800, Yuanhan Liu wrote:
> > > > > > > This reverts commit d1f8b30ec8dde0318fd1b98d24a64926feae9625.
> > > > > > > 
> > > > > > > It turned out that it breaks stuff, so revert it:
> > > > > > > 
> > > > > > >     http://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg00949.html
> > > > > > > 
> > > > > > > CC: "Michael S. Tsirkin" <mst@redhat.com>
> > > > > > > Reported-by: Paolo Bonzini <pbonzini@redhat.com>
> > > > > > > Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
> > > > > > 
> > > > > > OK but that's not enough. We need to also
> > > > > > - drop patch sending this on stop
> > > > > 
> > > > > I could do that. But may I know why we have to drop it on stop?
> > > > 
> > > > Because we need to get the state from remote after stop.
> > > > RESET_OWNER discards that, so we can't resume the VM.
> > > > 
> > > > > If we don't send it on stop, when will we send it? The termination
> > > > > of QEMU?
> > > > 
> > > > If mq is negotiated, we don't need it.  If mq isn't negotiated, maybe we
> > > > should send it on reset/driver unload.
> > > 
> > > Sorry, what place do you mean exactly?
> > 
> > There's no such code - you'll have to add
> > a callback into vhost from virtio.
> 
> Say, at virtio_net_reset()?
> 
> 	--yliu

Sounds good.

> > > 
> > > > It might be better than
> > > > corrupting guest memory. And if we do, maybe we should keep
> > > > the RESET_DEVICE name.

      reply	other threads:[~2015-10-21 10:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16  7:18 [Qemu-devel] [PATCH 1/3] Revert "vhost: rename VHOST_RESET_OWNER to VHOST_RESET_DEVICE" Yuanhan Liu
2015-10-16  7:19 ` [Qemu-devel] [PATCH 2/3] doc: vhost-user: request naming fix Yuanhan Liu
2015-10-16  7:19 ` [Qemu-devel] [PATCH 3/3] vhost-user-test: add multiple queue test Yuanhan Liu
2015-10-16  7:20   ` Michael S. Tsirkin
2015-10-16  7:33     ` Yuanhan Liu
2015-10-16  7:21 ` [Qemu-devel] [PATCH 1/3] Revert "vhost: rename VHOST_RESET_OWNER to VHOST_RESET_DEVICE" Michael S. Tsirkin
2015-10-16  7:32   ` Yuanhan Liu
2015-10-16  7:47     ` Michael S. Tsirkin
2015-10-16  8:04       ` Yuanhan Liu
2015-10-16  8:15         ` Michael S. Tsirkin
2015-10-16  8:38           ` Yuanhan Liu
2015-10-21  8:55       ` Yuanhan Liu
2015-10-21  9:15         ` Michael S. Tsirkin
2015-10-21  9:21           ` Yuanhan Liu
2015-10-21 10:42             ` Michael S. Tsirkin [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=20151021134130-mutt-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yuanhan.liu@linux.intel.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.