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/
Home Products Support Community News


Re: [Xen-ia64-devel] Time for hybrid virtualization?

To: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
Subject: Re: [Xen-ia64-devel] Time for hybrid virtualization?
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Thu, 17 Jan 2008 12:57:22 +0900
Cc: Alex Williamson <alex.williamson@xxxxxx>, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 16 Jan 2008 19:57:40 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <51CFAB8CB6883745AE7B93B3E084EBE20166FCAB@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>
References: <1200528127.6773.88.camel@lappy> <51CFAB8CB6883745AE7B93B3E084EBE20166FCAB@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
On Thu, Jan 17, 2008 at 11:06:55AM +0800, Xu, Anthony wrote:
> There were some issues we encounterd on building Vti-dom0( there is no
> modification for dom0 linux kernel at all),
> 1. need an interrupt vector to handle event channel,
>       how to reserve an interrupt vector?
>       What's the interrupt vector priority?
> 2. When dom0 wants to map other Vti-domain memory, dom0 don't have
> physical address space for it,
>       so foreign mapped guest memory don't have responding dom0 guest
> physical address.
>       This may have heavy impact on the infrastructure on dom0. We
> need to resolve it.
> If we use hybrid mode, above two issues can be resolved with current
> method.
> Hybrid mode is to use VT-I technology to virtualize CPU.

Interesting. The issue 2 can be easily resolved, I think.
It would be simply the privcmd device driver.

Do you have any idea about the environment detection(native, xen, kvm...)?

Xen-ia64-devel mailing list