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-ia64-devel

RE: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

To: "Alex Williamson" <alex.williamson@xxxxxx>, "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Thu, 13 Apr 2006 09:06:07 +0800
Cc: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 12 Apr 2006 18:07:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZeRd3taItZIGnqQEGedLubd6eohwAToBNA
Thread-topic: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches
>From: Alex Williamson [mailto:alex.williamson@xxxxxx]
>Sent: 2006年4月12日 23:29
>
>On Wed, 2006-04-12 at 09:01 +0100, Tristan Gingold wrote:
>
>> > Last, the only way to prevent such io access is from guest itself,
>> > meant not compiling native drivers in. Or else there's no way for
>> > xen to handle it correctly.
>> User should disable drivers in domU.  Everybody agree with that!
>
>   I don't.  Xen needs to handle this better.  domU I/O port space
>should be mapped to fault on access.  Writes should be dropped and
>reads
>return -1.  This is how a legacy system would behave.  We don't really
>care about performance here, I/O port space is already slow, and this is
>really only meant to handle startup time probing.  IMHO, it's
>unreasonable to ask users to disable all drivers or even try to tell
>them what that means.  The Linux/ia64 kernel currently does a pretty
>good job of not blindly probing address spaces looking for hardware.  I
>think as long as we handle I/O port space reasonably, we'll make the
>driver situation in domU more flexible.  Thanks,
>
>       Alex
>

Yes, it's better to emulate hardware behavior. 


Thanks,
Kevin

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