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: "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Wed, 12 Apr 2006 15:07:33 +0800
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 12 Apr 2006 00:07:50 -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: AcZd/2MjhR2LR1vARTuJuaqWawngTAAACSbg
Thread-topic: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches
>From: Tristan Gingold [mailto:Tristan.Gingold@xxxxxxxx]
>Sent: 2006年4月12日 15:08
>Le Mercredi 12 Avril 2006 08:12, Tian, Kevin a écrit :
>> From: Isaku Yamahata [mailto:yamahata@xxxxxxxxxxxxx]
>[...]
>> >That's an access to keyboard port possibly because now xen0/xenU
>> >
>> >> is compiled as one image with more drivers added. Maybe it's
>better
>> >> for us to map all 64M mmio area of domU to a dummy page at
>current
>> >> stage, to remove warnings and walk around some native drivers
>> >> within domU. Later when driver domain is added, we can map
>specific
>> >> mmio page to machine mmio range per configuration.
>> >
>> >I agree with you.
>> >But this issues isn't specific to the P2M/VP patch.
>I don't agree with this solution.  I really prefer to have warnings because
>it
>means something got wrong.  domU shouldn't access to mmio.
>
>If you use a dummy page, a device driver may loop.
>

Either way. Currently return 0 after warning actually same as dummy 
page.

Thanks,
Kevin

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

<Prev in Thread] Current Thread [Next in Thread>