From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:36275)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nikunj@linux.vnet.ibm.com>) id 1XYpbf-0006Ro-Up
	for qemu-devel@nongnu.org; Tue, 30 Sep 2014 01:04:20 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <nikunj@linux.vnet.ibm.com>) id 1XYpbW-0001hk-Ss
	for qemu-devel@nongnu.org; Tue, 30 Sep 2014 01:04:11 -0400
Received: from e28smtp01.in.ibm.com ([122.248.162.1]:39441)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nikunj@linux.vnet.ibm.com>) id 1XYpbV-0001g9-5K
	for qemu-devel@nongnu.org; Tue, 30 Sep 2014 01:04:02 -0400
Received: from /spool/local
	by e28smtp01.in.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use
	Only! Violators will be prosecuted
	for <qemu-devel@nongnu.org> from <nikunj@linux.vnet.ibm.com>;
	Tue, 30 Sep 2014 10:33:49 +0530
Received: from d28relay03.in.ibm.com (d28relay03.in.ibm.com [9.184.220.60])
	by d28dlp03.in.ibm.com (Postfix) with ESMTP id 52E23125804B
	for <qemu-devel@nongnu.org>; Tue, 30 Sep 2014 10:34:29 +0530 (IST)
Received: from d28av04.in.ibm.com (d28av04.in.ibm.com [9.184.220.66])
	by d28relay03.in.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id
	s8U564a666978006
	for <qemu-devel@nongnu.org>; Tue, 30 Sep 2014 10:36:04 +0530
Received: from d28av04.in.ibm.com (localhost [127.0.0.1])
	by d28av04.in.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id
	s8U53j9m013532
	for <qemu-devel@nongnu.org>; Tue, 30 Sep 2014 10:33:46 +0530
From: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
In-Reply-To: <20140929233030.5b27c593@bahia.local>
References: <1411066387-30889-1-git-send-email-mst@redhat.com>
	<1411066387-30889-15-git-send-email-mst@redhat.com>
	<20140922192857.18930639@bahia.local>
	<20140929161505.GC21268@redhat.com>
	<20140929233030.5b27c593@bahia.local>
Date: Tue, 30 Sep 2014 10:33:31 +0530
Message-ID: <87h9zpya1o.fsf@linux.vnet.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain
Subject: Re: [Qemu-devel] [PULL v3 14/15] virtio-pci: fix migration for pci
	bus master
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, Jason Wang <jasowang@redhat.com>, qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>, Alexander Graf <agraf@suse.de>

Greg Kurz <gkurz@linux.vnet.ibm.com> writes:
> On Mon, 29 Sep 2014 19:15:05 +0300
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> It may be possible to change the way SLOF configures the virtq so
> that it wouldn't suffer from the device being reset. We have some
> time left before 2.2. I have a tentative patch for SLOF that I'll
> be glad to share with Nikunj ASAP.

virtio-block is straight forward. I think we will have similar problem
with virtio-scsi as well. That driver will be tricky as it is
inter-linked with generic scsi code in SLOF.

Regards
Nikunj