From: Anthony Liguori <anthony@codemonkey.ws>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu list <qemu-devel@nongnu.org>, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH master/0.14] virtio-serial: Make sure virtqueue is ready before discarding data
Date: Mon, 07 Feb 2011 20:25:59 -0600 [thread overview]
Message-ID: <4D50A9B7.7040004@codemonkey.ws> (raw)
In-Reply-To: <20110208021422.GA691@amit-x200.redhat.com>
On 02/07/2011 08:14 PM, Amit Shah wrote:
> On (Sun) 06 Feb 2011 [11:50:46], Amit Shah wrote:
>
>> On (Fri) 04 Feb 2011 [06:52:04], Anthony Liguori wrote:
>>
>>> On 02/04/2011 02:54 AM, Amit Shah wrote:
>>>
>>>> This can happen if a port gets unplugged before guest has chance to
>>>> initialise vqs.
>>>>
>>>> Reported-by: Juan Quintela<quintela@redhat.com>
>>>> Signed-off-by: Amit Shah<amit.shah@redhat.com>
>>>>
>>> Applied to master, Thanks.
>>>
>> What's the strategy to commit to 0.14?
>>
> Nevermind; saw it in the last pull.
>
Yes, but if we decide to make this a subsection, we may need to revert
this before the 0.14.0 release because once 0.14.0 goes out, we can't go
back and change it.
If that's how you want to approach it, then please send the revert
patches. The flow_control=0 patches you sent out before definitely
aren't the right approach for migration compatibility.
Regards,
Anthony Liguori
> Amit
>
>
next prev parent reply other threads:[~2011-02-08 2:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 8:54 [Qemu-devel] [PATCH master/0.14] virtio-serial: Make sure virtqueue is ready before discarding data Amit Shah
2011-02-04 12:11 ` [Qemu-devel] " Juan Quintela
2011-02-04 12:52 ` [Qemu-devel] " Anthony Liguori
2011-02-06 6:20 ` Amit Shah
2011-02-08 2:14 ` Amit Shah
2011-02-08 2:25 ` Anthony Liguori [this message]
2011-02-08 2:55 ` Amit Shah
2011-02-08 7:40 ` Anthony Liguori
2011-02-08 7:55 ` Amit Shah
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=4D50A9B7.7040004@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=amit.shah@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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.