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] RE: pv_ops polish: config option & head file

To: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Subject: RE: [Xen-ia64-devel] RE: pv_ops polish: config option & head file
From: Alex Williamson <alex.williamson@xxxxxx>
Date: Mon, 17 Mar 2008 21:54:52 -0600
Cc: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 17 Mar 2008 20:55:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <10EA09EFD8728347A513008B6B0DA77A02EBBC91@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Organization: HP OSLO R&D
References: <7ktzjbqjfs.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20080313124404.GA2687@saphi> <10EA09EFD8728347A513008B6B0DA77A02E77732@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080314084609.GL22951%yamahata@xxxxxxxxxxxxx> <10EA09EFD8728347A513008B6B0DA77A02E777F6@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1205514823.8100.30.camel@lappy> <10EA09EFD8728347A513008B6B0DA77A02EBB71D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1205766861.7008.11.camel@lappy> <10EA09EFD8728347A513008B6B0DA77A02EBBC91@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2008-03-18 at 11:36 +0800, Dong, Eddie wrote:
> > 
> >    I think CONFIG_XEN might become something like CONFIG_PARAVIRT_XEN,
> > which will be dependent on CONFIG_PARAVIRT.  There might also be
> > CONFIG_PARAVIRT_LGUEST, CONFIG_PARAVIRT_KVM, etc...  I think that
> 
> Then a single image won't be able to run on both lguest/Xen/KVM. This is
> worse than running_on_xen dynamic condition check.

   Huh?  I never said you couldn't enable more than one
CONFIG_PARAVIRT_FOO flavor in the same binary.

        Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


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

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