All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: mukesh.rathor@oracle.com
Cc: xen-devel@lists.xensource.com
Subject: Re: XENFEAT_supervisor_mode_kernel ???
Date: Thu, 20 Nov 2008 23:07:33 +0000	[thread overview]
Message-ID: <C54B9E35.1F752%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4925ECB9.4010706@oracle.com>

No, not really. The hypervisor changes could likely not be that large.

 -- Keir

On 20/11/08 23:03, "Mukesh Rathor" <mukesh.rathor@oracle.com> wrote:

> Oh, cool. I was looking at syscalls on PV x86_64 guests, and one of my
> thoughts was running in HVM mode but do all MMU stuff using hypercalls like
> PV. Other than having to change the hyp domain create portions, setting things
> up, is there a technical reason it can't be done today... thanks, Mukesh
> 
> Keir Fraser wrote:
>> On 20/11/08 22:42, "Mukesh Rathor" <mukesh.rathor@oracle.com> wrote:
>> 
>>> I'm trying ot figure out what that's all about? I see in 64 PV domU, it's
>>> being checked prior to returning from syscall.  On the xen side, I see it
>>> tied
>>> to supervisor_mode_kernel, but the only info I find is changelog comment
>>> which
>>> suggests it's purpose is to allow dom0 run in ring 0... So why the check in
>>> a
>>> domU kernel?
>> 
>> It's useful if the hypervisor runs the guest kernel in ring 0. Current Xen
>> doesn't do that, but in future we may run 64-bit PV guests in HVM context as
>> that may actually be faster.
>> 
>>  -- Keir
>> 

  reply	other threads:[~2008-11-20 23:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 22:42 XENFEAT_supervisor_mode_kernel ??? Mukesh Rathor
2008-11-20 22:55 ` Keir Fraser
2008-11-20 23:03   ` Mukesh Rathor
2008-11-20 23:07     ` Keir Fraser [this message]
2008-11-24  1:11     ` Jeremy Fitzhardinge
2008-11-24 22:37       ` Mukesh Rathor

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=C54B9E35.1F752%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=mukesh.rathor@oracle.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.