All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yu Zhang <yu.c.zhang@linux.intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: about fully UMIP support in Xen
Date: Wed, 19 Apr 2017 21:50:34 +0800	[thread overview]
Message-ID: <58F76B2A.3070702@linux.intel.com> (raw)
In-Reply-To: <58F7837D0200007800151F53@prv-mh.provo.novell.com>



On 4/19/2017 9:34 PM, Jan Beulich wrote:
>>>> On 19.04.17 at 13:44, <yu.c.zhang@linux.intel.com> wrote:
>> On 4/19/2017 7:19 PM, Jan Beulich wrote:
>>>>>> On 19.04.17 at 11:48, <yu.c.zhang@linux.intel.com> wrote:
>>>> Does hypervisor need to differentiate dom0 kernel and its
>>>> user space?
>>> If we want to para-virtualize the feature, then yes. Otherwise
>>> we can't assume the guest kernel would deal with user mode faults,
>>> so we'd have to. Arguably there could be a non-default mode in
>>> which we don't (forcing such applications to get a signal or crash).
>> For UMIP is to be para-virtualized,  is it OK to give dom0 kernel the
>> physical value
>> if instructions are triggered in the kernel?
> Why would you want to special case Dom0 here? I don't see
> anything wrong with giving Dom0 the real values, but since you'll
> have to not give DomU-s the real values, you'd then add more
> code to treat Dom0 specially. Simply give everyone fake values.

Oh. So in such case should return 0 to the dom0 kernel I guess?

Here come a dumb question: does other pv domain also run in ring 3 in 
vmx root mode,
or simply in vmx non-root ring 0?  :)

Thanks
Yu

>> And if the instructions are triggered in dom0 user space, the spec
>> requires a #GP
>> fault, and we can return 0 to the application in the #GP fault handler,
>> is it OK?
> Yes, I think so. But the fundamental rule is - make it match what
> native Linux does in that case.
>
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-04-19 13:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19  8:48 about fully UMIP support in Xen Yu Zhang
2017-04-19  9:18 ` Jan Beulich
2017-04-19  9:48   ` Yu Zhang
2017-04-19  9:59     ` Andrew Cooper
2017-04-19 11:16       ` Yu Zhang
2017-04-19 11:19     ` Jan Beulich
2017-04-19 11:44       ` Yu Zhang
2017-04-19 13:34         ` Jan Beulich
2017-04-19 13:49           ` Andrew Cooper
2017-04-19 14:06             ` Jan Beulich
2017-04-19 14:17               ` Andrew Cooper
2017-04-19 14:27                 ` Jan Beulich
2017-04-19 14:35                   ` Andrew Cooper
2017-04-19 13:50           ` Yu Zhang [this message]
2017-04-19 13:58             ` Andrew Cooper
2017-04-19 14:07               ` Jan Beulich
2017-04-19 14:09                 ` Andrew Cooper
2017-04-20  7:15                   ` Yu Zhang
2017-04-20  9:47                     ` Jan Beulich
2017-04-20  9:53                       ` Yu Zhang
2017-04-20 10:01                         ` Jan Beulich
2017-04-20 10:10                           ` Yu Zhang
2017-04-20 10:23                             ` Andrew Cooper
2017-04-20 10:38                               ` Yu Zhang

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=58F76B2A.3070702@linux.intel.com \
    --to=yu.c.zhang@linux.intel.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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.