WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [PATCH 0/5] pcie io space multiplexing for bootable pass

To: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH 0/5] pcie io space multiplexing for bootable pass through HVM domain
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Fri, 29 May 2009 10:27:14 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "shimada-yxb@xxxxxxxxxxxxxxx" <shimada-yxb@xxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Ian.Jackson@xxxxxxxxxxxxx" <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Thu, 28 May 2009 19:29:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090528105218.GA32399%yamahata@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20090528034648.GA9392@xxxxxxxxxxxxxxxxxxxxxxxxxx> <0A882F4D99BBF6449D58E61AAFD7EDD62EEF1952@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20090528105218.GA32399%yamahata@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnfgmDl4NVTe/ojRHiOREKawqAjLgAggpHw
Thread-topic: [Xen-devel] [PATCH 0/5] pcie io space multiplexing for bootable pass through HVM domain
>From: Isaku Yamahata [mailto:yamahata@xxxxxxxxxxxxx] 
>Sent: 2009年5月28日 18:52
>> How about same box used
>> in native environment, where how admin can judge which PCI-e slot
>> is allocated with I/O ports for bootable purpose?
>
>I'm not sure I understand your point.
>You mean there should be a way for an admin to know easily 
>which pcie slot
>is specified?
>The admins should know what they did. They know what kernel 
>command line
>they passed to the kernel. or /proc/cmdline.
>

In a native case, as you said, only 16 or fewer (if legacy ISA card
exists) PCI-e slots can be assigned with I/O resources. Say an
admin wants to insert a bootable card. How can this guy know 
which slot will be granted with I/O resources by kernel? Does 
native Linux provide similar cmdline as your approach to assign
which slot to be I/O capable? Or admin has to use lspci with
assumption that next boot kernel will assign I/O in same way?

Not relevant to your patch here. Just interested about how this
big box works on native.

Thanks,
Kevin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel