From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58309)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1XEHcA-0008BQ-02
	for qemu-devel@nongnu.org; Mon, 04 Aug 2014 08:43:52 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1XEHc3-0000Me-QV
	for qemu-devel@nongnu.org; Mon, 04 Aug 2014 08:43:45 -0400
Received: from mx1.redhat.com ([209.132.183.28]:54990)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1XEHc3-0000MY-Im
	for qemu-devel@nongnu.org; Mon, 04 Aug 2014 08:43:39 -0400
Date: Mon, 4 Aug 2014 14:43:58 +0200
From: "Michael S. Tsirkin" <mst@redhat.com>
Message-ID: <20140804124358.GE15491@redhat.com>
References: <CACrq+iL7XJ7kt4aD+oMPcQD+_s3y8ygNAkVK2LJyK4c1ZXWhDg@mail.gmail.com>
	<20140730131605.GA25923@redhat.com>
	<CACrq+iLkYP1vhTfwfTFMuv5x69FZOkuAtshiC1PCWOOX_qhKmg@mail.gmail.com>
	<1406731566.2963.53.camel@ul30vt.home>
	<CACrq+iKb4fSqUdGmZe2ECWesrZYn_72QAUe+oXo_U=MWCw5iew@mail.gmail.com>
	<1406906753.2963.188.camel@ul30vt.home>
	<1406910924.2963.227.camel@ul30vt.home> <53DBC2C4.3030801@web.de>
	<1406913384.2963.232.camel@ul30vt.home> <53DC7D16.1050509@web.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <53DC7D16.1050509@web.de>
Subject: Re: [Qemu-devel] vfio in the guest: no available reset mechanism
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: Jan Kiszka <jan.kiszka@web.de>
Cc: Alex Williamson <alex.williamson@redhat.com>, Le Tan <tamlokveer@gmail.com>, qemu-devel <qemu-devel@nongnu.org>

On Sat, Aug 02, 2014 at 07:54:30AM +0200, Jan Kiszka wrote:
> On 2014-08-01 19:16, Alex Williamson wrote:
> >>  Also, it may let some of our device
> >> models deviate from their real versions (I suppose, e.g., none of the
> >> e1000 devices we currently emulate exposed FLR).
> > 
> > Of course, but what are the chances that the driver will care?
> 
> No drivers of GPOSes, but special or legacy OSes may do so. Keep in mind
> that Intel e.g. is documenting their PCI devices with fixed config space
> addresses for their capability.
> 
> Also, we completely lack PM caps so far. Adding them would already have
> the value of increasing emulation accuracy. And here I think we are free
> to always implement reset behavior behind D3->D0 transitions. So my
> believe is that this will be the better path.
> 
> Jan
> 
> 


That's true but is PM reset per-function or per-device?
I'll have to check the spec - do you happen to rememeber?