From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: Jun Nakajima <jun.nakajima@intel.com>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
Donald D Dugger <donald.d.dugger@intel.com>
Subject: Re: Re: pvclock in userland (reprise)
Date: Mon, 21 Sep 2009 11:54:14 -0700 [thread overview]
Message-ID: <4AB7CBD6.6060202@goop.org> (raw)
In-Reply-To: <4AB753840200007800015E72@vpn.id2.novell.com>
On 09/21/09 01:20, Jan Beulich wrote:
>> Does Xen still claim the top part of the 32-bit address space?
>>
> Sure - currently just for the compat M2P table. I can't see why other
> things could be mapped there (the compat M2P table is at most 128M
> in size, hence there's plenty of virtual space available).
>
Yep, we could alias the pvclock info there, though I'm coming to like
the idea of doing it via syscall/hypercall rather than having the guest
explicitly get access to shared memory.
J
prev parent reply other threads:[~2009-09-21 18:54 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
2009-09-19 10:47 ` Keir Fraser
2009-09-21 8:20 ` Jan Beulich
2009-09-21 18:54 ` Jeremy Fitzhardinge [this message]
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=4AB7CBD6.6060202@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.