From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=53713 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PJPhG-00059P-D2
	for qemu-devel@nongnu.org; Fri, 19 Nov 2010 07:04:07 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1PJPhF-0003Ub-Au
	for qemu-devel@nongnu.org; Fri, 19 Nov 2010 07:04:06 -0500
Received: from mx1.redhat.com ([209.132.183.28]:57074)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1PJPhF-0003UI-42
	for qemu-devel@nongnu.org; Fri, 19 Nov 2010 07:04:05 -0500
Date: Fri, 19 Nov 2010 14:03:26 +0200
From: "Michael S. Tsirkin" <mst@redhat.com>
Message-ID: <20101119120326.GB5713@redhat.com>
References: <4bdfece02df439b60dae92dfc59e903353176218.1289895735.git.yamahata@valinux.co.jp>
	<cover.1290002681.git.mst@redhat.com>
	<20101119094226.GB16942@valinux.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20101119094226.GB16942@valinux.co.jp>
Subject: [Qemu-devel] Re: [PATCH 0/2] Re: [PATCH v9 5/8] pcie/aer: helper
 functions for pcie aer capability
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/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: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: skandasa@cisco.com, adnan@khaleel.us, etmartin@cisco.com, qemu-devel@nongnu.org, wexu2@cisco.com

On Fri, Nov 19, 2010 at 06:42:27PM +0900, Isaku Yamahata wrote:
> On Wed, Nov 17, 2010 at 04:06:38PM +0200, Michael S. Tsirkin wrote:
> > Please, try to address the TODO: I think the case of
> > PCIE device behind a pci bridge is not covered properly.
> 
> Right, pci-to-pcie bridge case isn't covered.
> Although SERR bit can be set, the error can't be propagated up further
> because qemu doesn't emulate PERR#/SERR#.
> 
> There is no use case of pci-to-pcie bridge in qemu, I think.

I think it's useful to put an express device behind
a pci bridge in qemu, because pci bridges are tested
and supported by more guests.

> If good error handling is wanted, express should be used.
> So it isn't worthwhile to implement pci-to-pcie bridge.

Okay, we can look into this later.

> -- 
> yamahata