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

xen-devel

[Top] [All Lists]

[Xen-devel] Re: Xen: Hybrid extension patchset for hypervisor

To: "Yang, Sheng" <sheng.yang@xxxxxxxxx>
Subject: [Xen-devel] Re: Xen: Hybrid extension patchset for hypervisor
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: 2009年9月16日 10:08:20 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Eddie Dong <eddie.dong@xxxxxxxxx>, Jun Nakajima <jun.nakajima@xxxxxxxxx>
Delivery-date: 2009年9月16日 02:09:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200909161644.45707.sheng.yang@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aco2qgOpAbnFc0gaRB2pnHUmRWzAOwAAzh81
Thread-topic: Xen: Hybrid extension patchset for hypervisor
User-agent: Microsoft-Entourage/12.20.0.090605
On 16/09/2009 09:44, "Yang, Sheng" <sheng.yang@xxxxxxxxx> wrote:
> Hi Keir & Jeremy
>
> Here is the hypervisor part of hybrid extension support.
>
> Please review, thanks!
The principle is okay I guess. These changes would have to be trickled in
with a really good explanation and justification for each one. For example,
I'm not clear why the enable-hybrid hypercall is needed. Why not just
provide access to evtchn and timer hypercalls always, and guest sues them if
it is capable of it? I'm also not sure why PV timer events get routed to
irq0 -- why not via an event channel as usual, now that you are enabling HVM
guests to use the evtchn subsystem? What's a hybrid gnttab, and why does it
need an explciit reserved e820 region? And so on.
The general principle of these patches seems to be to create a set of
individual, and perhaps largely independent, accelerations/enlightenments to
the HVM interface. I can at least agree with and support that aim.
 -- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: [Xen-devel] Re: [RFC][PATCH 08/10] x86: Don't ack_APIC_irq() if lapic is disabled in GENERIC_INTERRUPT_VECTOR handler , Cyrill Gorcunov
Next by Date: Re: [Xen-devel] [PATCH] x86 hvm: freeze PIT/LAPIC timer emulation while its IRQ is masked , Keir Fraser
Previous by Thread: [Xen-devel] Xen: Hybrid extension patchset for hypervisor , Yang, Sheng
Next by Thread: [Xen-devel] Re: Xen: Hybrid extension patchset for hypervisor , Keir Fraser
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /