From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Is: pci=assign-busses blows up Xen 4.4
Date: Mon, 24 Feb 2014 11:15:24 -0500
Message-ID: <20140224161524.GJ816@phenom.dumpdata.com>
References: <52DFC2DA0200007800115C79@nat28.tlf.novell.com>
	<20140122214034.GB9460@phenom.dumpdata.com>
	<52E0DFBB0200007800116041@nat28.tlf.novell.com>
	<20140124150128.GF12946@phenom.dumpdata.com>
	<52E2A0930200007800116CAE@nat28.tlf.novell.com>
	<20140124174349.GA15472@phenom.dumpdata.com>
	<20140124215652.GA18710@phenom.dumpdata.com>
	<20140205200708.GA9278@phenom.dumpdata.com>
	<20140221191833.GA8812@phenom.dumpdata.com>
	<530B1BD3020000780011E9B8@nat28.tlf.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <530B1BD3020000780011E9B8@nat28.tlf.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>, Andrew Cooper <andrew.cooper3@citrix.com>, Xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

On Mon, Feb 24, 2014 at 09:15:47AM +0000, Jan Beulich wrote:
> >>> On 21.02.14 at 20:18, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > 4). Make Xen do the bus re-assignment.
> > 
> > The attached patch is an interesting "solution" to the BIOS
> > not doing the right bus-extending with SR-IOV devices.
> 
> Nice that you got this to work, but this is definitely not the route
> to go: There's no way we can guarantee to do this re-numbering

<nods>

> on segments other than segment 0 (since we can't necessarily
> access the config spaces of the devices on other segments
> before Dom0 telling us necessary bits of information).
>
Correct.
 
> Apart from that, I'd also really like to avoid duplicating code from
> Linux into the hypervisor when all that is needed is making that
> code work right in an admittedly rather special case.

<nods>
> 
> Jan
>