From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>,
Donald D Dugger <donald.d.dugger@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: Re: pvclock in userland (reprise)
Date: Fri, 18 Sep 2009 17:33:29 -0700 [thread overview]
Message-ID: <4AB426D9.1080309@goop.org> (raw)
In-Reply-To: <C6D8FE05.15275%keir.fraser@eu.citrix.com>
On 09/18/09 01:06, Keir Fraser wrote:
> On 18/09/2009 08:29, "Jan Beulich" <JBeulich@novell.com> wrote:
>
>
>>> I don't think mapping things into application address space is really
>>> possible without guest kernel changes. The guest kernel owns and manages the
>>> pte that you'd be overwriting. Just blatting the pte would not be good form.
>>>
>> Unless they sit in Xen's virtual space.
>>
> Oh yes, I remember we talked about that before. That is possible, but the
> design fell down on other points. I think guest kernel involvement, even if
> only as a kernel driver, should make this more tractable.
>
Xen's memory isn't mappable in a 32-bit compat domain, so you'd need to
come up with something else there. Does Xen still claim the top part of
the 32-bit address space?
J
next prev parent reply other threads:[~2009-09-19 0:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 17:58 pvclock in userland (reprise) Dan Magenheimer
2009-09-17 19:03 ` Keir Fraser
2009-09-17 19:13 ` Nakajima, Jun
2009-09-17 19:23 ` Keir Fraser
2009-09-17 19:24 ` Jeremy Fitzhardinge
2009-09-17 19:45 ` Dan Magenheimer
2009-09-17 20:13 ` Jeremy Fitzhardinge
2009-09-17 20:57 ` Dan Magenheimer
2009-09-18 7:29 ` Jan Beulich
2009-09-18 8:06 ` Keir Fraser
2009-09-19 0:33 ` Jeremy Fitzhardinge [this message]
2009-09-19 10:47 ` Keir Fraser
2009-09-21 8:20 ` Jan Beulich
2009-09-21 18:54 ` Jeremy Fitzhardinge
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=4AB426D9.1080309@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@novell.com \
--cc=dan.magenheimer@oracle.com \
--cc=donald.d.dugger@intel.com \
--cc=jun.nakajima@intel.com \
--cc=keir.fraser@eu.citrix.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.