qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [vhost-user] Expectations around reconnection
Date: Thu, 13 May 2021 11:43:25 +0200	[thread overview]
Message-ID: <6eded3ad-ea69-3d07-65ee-01d4ac7cf067@redhat.com> (raw)
In-Reply-To: <BY5PR11MB44014FC44FFAC6976FC89BC1EA539@BY5PR11MB4401.namprd11.prod.outlook.com>

Cc'ing few developers

On 5/11/21 3:33 PM, Boeuf, Sebastien wrote:
> Hi All,
> 
> In the context of vhost-user, I was wondering how a reconnection should
> be handled from the VMM perspective?
> 
> In particular, I'm looking at the OVS-DPDK use case using the client 
> mode (meaning QEMU acts as the server), and I'd like to understand what 
> QEMU does to handle this. Upon disconnection from the backend, does QEMU
>  reset the virtio device (meaning the guest
> is notified about it)? And upon the new connection from the backend, 
> does QEMU go through the whole vhost-user initialization once again 
> (feature acknowledgement, setup of vrings, etc...), or does it simply 
> assume the backend will have saved all these information?
> 
> Thanks for your time,
> Sebastien



  reply	other threads:[~2021-05-13  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 13:33 [vhost-user] Expectations around reconnection Boeuf, Sebastien
2021-05-13  9:43 ` Philippe Mathieu-Daudé [this message]
2021-05-13 13:34   ` Stefan Hajnoczi

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=6eded3ad-ea69-3d07-65ee-01d4ac7cf067@redhat.com \
    --to=philmd@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sebastien.boeuf@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).