From: Frank van der Linden <Frank.Vanderlinden@Sun.COM>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "Yang, Sheng" <sheng.yang@intel.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Eddie Dong <eddie.dong@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: Re: Xen: Hybrid extension patchset for hypervisor
Date: Wed, 16 Sep 2009 13:11:49 -0600 [thread overview]
Message-ID: <4AB13875.9020703@Sun.COM> (raw)
In-Reply-To: <C6D66994.14D6A%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> On 16/09/2009 09:44, "Yang, Sheng" <sheng.yang@intel.com> 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
>
I did not see the hypervisor part of these patches appear in my
xen-devel inbox. Is this a problem on my end, or were they not sent to
the list? If so, I'm interested in them, so it'd be great if they could
be sent to the list.
Thanks,
- Frank
next prev parent reply other threads:[~2009-09-16 19:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 8:44 Xen: Hybrid extension patchset for hypervisor Yang, Sheng
2009-09-16 9:08 ` Keir Fraser
2009-09-16 14:04 ` Keir Fraser
2009-09-16 16:28 ` Nakajima, Jun
2009-09-16 18:19 ` Jeremy Fitzhardinge
2009-09-16 21:12 ` Ian Campbell
2009-09-16 21:22 ` Jeremy Fitzhardinge
2009-09-17 9:16 ` Ian Campbell
2009-09-17 15:56 ` Nakajima, Jun
2009-09-17 17:34 ` Jeremy Fitzhardinge
2009-09-19 0:17 ` Nakajima, Jun
2009-09-19 0:28 ` Jeremy Fitzhardinge
2009-09-17 17:19 ` Jeremy Fitzhardinge
2009-09-16 19:11 ` Frank van der Linden [this message]
2009-09-17 6:13 ` Yang, Sheng
2009-09-17 6:25 ` Keir Fraser
2009-09-17 6:30 ` Sheng Yang
2009-09-17 6:47 ` Yang, Sheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AB13875.9020703@Sun.COM \
--to=frank.vanderlinden@sun.com \
--cc=eddie.dong@intel.com \
--cc=jeremy@goop.org \
--cc=jun.nakajima@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=sheng.yang@intel.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.