[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] Transparent paravirtualization is broken


  • To: "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Wed, 3 May 2006 10:22:53 -0700
  • Delivery-date: Wed, 03 May 2006 10:23:27 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZuvooehwVUbFOJT1uMxgD1WDokeQAFrNJg
  • Thread-topic: [Xen-ia64-devel] Transparent paravirtualization is broken

Historically, we've put a call to xen_init() in any
driver initialization that might run on Xen but shouldn't
when running native.

Hollis is very much against that approach but we've
continued to use it just because it is simple and
effective.  Hollis' approach is probably better but
nobody has tested it or provided a patch.

Some of the discussion is at:
http://lists.xensource.com/archives/html/xen-devel/2005-09/msg00881.html


> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Tristan Gingold
> Sent: Wednesday, May 03, 2006 8:37 AM
> To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-ia64-devel] Transparent paravirtualization is broken
> 
> Hi,
> 
> due to late_initcall and postcore_initcall in xenbus_probe.c 
> (at least), 
> transparent paravirtualization is currently broken.
> What is the standard way to deal with such issues ?
> 
> Tristan.
> 
> 
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
> 

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.