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: tgingold@xxxxxxx
Date: Thu, 17 Jan 2008 10:26:47 +0100
Cc: Alex Williamson <alex.williamson@xxxxxx>, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 17 Jan 2008 01:27:00 -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: Internet Messaging Program (IMP) 3.2.8
Quoting "Xu, Anthony" <anthony.xu@xxxxxxxxx>:

> 1. Memory virtualization,
I agree.

> 2. CPU virtualization
I agree.

>       Accessing shadow register may be faster than accessing memory.
... or not.  Reading memory is faster than reading most AR or CR regs.

>       In summary, I think there are similar performance in terms of
> cpu vitualization.
I agree but this depends on your CPU generation.  I don't know VTi differences
between Montvale and Montecito.

> 3. Device vitualiztion
>       Both para-domain and VT-I domain can use same technology.

4. Firmware
  Should we use a guest firmware for dom0 ?

> 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?

Almost resolved by PV on HVM drivers.


Xen-ia64-devel mailing list