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] [RFC] Disable xen platform device when it is not needed.

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC] Disable xen platform device when it is not needed.
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 23 Feb 2009 09:41:27 -0800
Cc: Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Kouya Shimura <kouya@xxxxxxxxxxxxxx>, James Harper <james.harper@xxxxxxxxxxxxxxxx>
Delivery-date: Mon, 23 Feb 2009 09:41:57 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <18850.56901.772904.385385@xxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmV3REh8gMIJFImSwOnKcttGfV/OQAAOLSY
Thread-topic: [Xen-devel] [RFC] Disable xen platform device when it is not needed.
User-agent: Microsoft-Entourage/12.15.0.081119
On 23/02/2009 09:35, "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx> wrote:

> Keir Fraser writes ("Re: [Xen-devel] [RFC] Disable xen platform device when it
> is not needed."):
>> On 23/02/2009 08:43, "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx> wrote:
>>> How will this interact with the `disable qemu PCI devices in HVM
>>> domains' feature, which also uses ioport 0x10 ?
>> 
>> That feature implements WORD and DWORD ports at address 0x10, but leaves the
>> BYTE port at that address available for other uses.
> 
> Ah, err, yes.  Ugh.  Maybe a table of uses of ioports 0x10 (and 0x12!)
> would be a sensible addition to xen-unstable.hg/doc/ somewhere.

Well, byte 0x10 is available and is the first one, so it seemed to make
sense to me. ;-) The protocol on the fixed ports is already kind of ugly and
makes use of different meanings for different access sizes, so it's in the
existing spirit also. More documentation is almost always nice, so I can't
disagree with that.

 -- Keir



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