From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=60425 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PmiBY-0007YR-9C for qemu-devel@nongnu.org; Tue, 08 Feb 2011 02:40:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PmiBX-0003LU-BZ for qemu-devel@nongnu.org; Tue, 08 Feb 2011 02:40:28 -0500 Received: from mail-wy0-f173.google.com ([74.125.82.173]:62220) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PmiBX-0003LO-67 for qemu-devel@nongnu.org; Tue, 08 Feb 2011 02:40:27 -0500 Received: by wyg36 with SMTP id 36so5692837wyg.4 for ; Mon, 07 Feb 2011 23:40:25 -0800 (PST) Message-ID: <4D50F359.7070002@codemonkey.ws> Date: Tue, 08 Feb 2011 01:40:09 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH master/0.14] virtio-serial: Make sure virtqueue is ready before discarding data References: <4D4BF674.5050305@codemonkey.ws> <20110206062046.GA1234@amit-x200.redhat.com> <20110208021422.GA691@amit-x200.redhat.com> <4D50A9B7.7040004@codemonkey.ws> <20110208025513.GE32178@amit-x200.redhat.com> In-Reply-To: <20110208025513.GE32178@amit-x200.redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Amit Shah Cc: qemu list , Juan Quintela On 02/07/2011 08:55 PM, Amit Shah wrote: > On (Mon) 07 Feb 2011 [20:25:59], Anthony Liguori wrote: > >> 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 >>>>>> Signed-off-by: Amit Shah >>>>>> >>>>> 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. >> > Right. > > However, virtio doesn't have vmstate yet. Are we willing to put vmstate > in 0.14 to introduce subsections? I doubt that. > Not, that's why I suggested reverting this change and pushing it to 0.15. We're not going to fix it properly in 0.14. Regards, Anthony Liguori >> 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. >> > I understand, I've not looked at that thread yet, but if we want to do > that for 0.14 w/o vmstate, that might be the only way. > > Amit > >