All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "Yang, Sheng" <sheng.yang@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"Dong, Eddie" <eddie.dong@intel.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>,
	"Nakajima, Jun" <jun.nakajima@intel.com>
Subject: Re: Re: Xen: Hybrid extension patchset for hypervisor
Date: Thu, 17 Sep 2009 10:19:47 -0700	[thread overview]
Message-ID: <4AB26FB3.4070600@goop.org> (raw)
In-Reply-To: <1253178985.16152.26.camel@zakaz.uk.xensource.com>

On 09/17/09 02:16, Ian Campbell wrote:
> In practise, at least for the 2.6.18-xen tree (which is the only one
> where I expect it was ever completely implemented), it is only used to
> set the kernel CS and DS and to gate sysenter setup (for which I think
> we have a better mechanism today) but you are right that in principle it
> could be more far reaching than that.
>   

Yeah.  Looks like the only other thing it allows is that the guest can
set arbitrary gdt entries.

>> Making use of XENFEAT_auto_translated_physmap would avoid the need for
>> identity p2m/m2p tables, but I'm not sure whether it still works.  I got
>> close to completely removing all references to it at one point, but I
>> think ia64 uses it?
>>     
> I very much expect that it'll need fixing/(re)implementing on both the
> kernel and hypervisor side...
>   

Yeah, I think the Xen side is missing altogether on x86 now.  I don't
think its worth recovering it unless its the ABI for making HAP
available to guests.  If IA64 is using it, then I think big parts of the
kernel are probably in OK shape (drivers, etc).

    J

  parent reply	other threads:[~2009-09-17 17:19 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 [this message]
2009-09-16 19:11   ` Frank van der Linden
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=4AB26FB3.4070600@goop.org \
    --to=jeremy@goop.org \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=jun.nakajima@intel.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.