All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tetsuya Mukawa <mukawa@igel.co.jp>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: jasowang@redhat.com, n.nikolaev@virtualopensystems.com,
	qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/5] Add feature to start QEMU without vhost-user backend
Date: Wed, 24 Jun 2015 16:13:39 +0900	[thread overview]
Message-ID: <558A58A3.5030506@igel.co.jp> (raw)
In-Reply-To: <20150624074815-mutt-send-email-mst@redhat.com>

On 2015/06/24 14:57, Michael S. Tsirkin wrote:
>>>>>> Also, if QEMU or the backend is closed unexpectedly, there is no way to
>>>>>> recover without restarting both applications.
>>>>> This was previously discussed:
>>>>> https://lists.gnu.org/archive/html/qemu-devel/2014-03/msg00585.html
>>>>> It doesn't look like any of the issues have been addressed.
>>>>>
>>>>> In my opinion, the right way to handle this requires
>>>>> guest cooperation.  For example, we can extend virtio 1 to allow a
>>>>> single queue to reset.
>>>>>
>>>>> We then can do something like the following:
>>>>> - hypervisor detects queue backend disconnect.
>>>>> - hypervisor sets flag and notifies guest
>>>>> - guest resets queue, optionally discarding queued packets
>>>>> - hypervisor detects (or requests if it's a client), backend reconnect
>>>>> - hypervisor detects guest queue reset
>>>>> - hypervisor notifies guests about backend reconnect
>>>>> - hypervisor sends hypervisor device state (e.g. queue addresses and
>>>>>   indices) to backend
>>>>>
>>>>> Reconnect isn't robust without such an extension.
>>>> I appreciate your all comments. It's truly helpful.
>>>> Do you have any plans to support such queue reset features in virtio spec?
>>> Maybe, but I don't have the time to work on this :(
>>> You are welcome to contribute this.
>> To do that, I need to talk around my boss to join OASIS :'(
> That's not true at all. Non members can submit feedback.
> You do need permission from your employer, but
> no need to join and pay fees if you don't want to.
> See
> https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=virtio
> for the details.

Thanks so much for correcting.

>> Probably it's not so easy, so I will just wait, if we need to change
>> spec itself.
> The QEMU patch that allows handling backend disconnect similar to
> disk errors can be implemented without guest/spec changes
> let me know if you need more explanation.

Could you please describe it more?
I want to try to implement it.

Regards,
Tetsuya

  reply	other threads:[~2015-06-24  7:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22  3:50 [Qemu-devel] [PATCH v2 0/5] Add feature to start QEMU without vhost-user backend Tetsuya Mukawa
2015-06-22  3:50 ` [Qemu-devel] [PATCH v2 1/5] vhost-user: Add ability to know vhost-user backend disconnection Tetsuya Mukawa
2015-06-22  3:50 ` [Qemu-devel] [PATCH v2 2/5] qemu-char: Add qemu_chr_disconnect to close a fd accepted by listen fd Tetsuya Mukawa
2015-06-22  3:50 ` [Qemu-devel] [PATCH v2 3/5] vhost-user: Shutdown vhost-user connection when wrong messages are passed Tetsuya Mukawa
2015-06-22  7:54   ` Michael S. Tsirkin
2015-06-23  8:33     ` Tetsuya Mukawa
2015-08-06 17:29   ` Marc-André Lureau
2015-06-22  3:50 ` [Qemu-devel] [PATCH v2 4/5] vhost-user: Enable 'nowait' and 'reconnect' option Tetsuya Mukawa
2015-08-06 17:41   ` Marc-André Lureau
2015-06-22  3:50 ` [Qemu-devel] [PATCH v2 5/5] vhost-user: Add new option to specify vhost-user backend supports Tetsuya Mukawa
2015-08-06 19:11   ` Marc-André Lureau
2015-06-22  8:14 ` [Qemu-devel] [PATCH v2 0/5] Add feature to start QEMU without vhost-user backend Michael S. Tsirkin
2015-06-23  8:31   ` Tetsuya Mukawa
2015-06-23  9:41     ` Michael S. Tsirkin
2015-06-24  5:46       ` Tetsuya Mukawa
2015-06-24  5:57         ` Michael S. Tsirkin
2015-06-24  7:13           ` Tetsuya Mukawa [this message]
2015-07-19 12:48           ` Michael S. Tsirkin
2015-07-22  2:44             ` Tetsuya Mukawa

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=558A58A3.5030506@igel.co.jp \
    --to=mukawa@igel.co.jp \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=n.nikolaev@virtualopensystems.com \
    --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.