All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mick Jordan <Mick.Jordan@sun.com>
To: Ian Pratt <Ian.Pratt@eu.citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: 2MB page PV guest support clarification
Date: Fri, 27 Feb 2009 16:42:43 -0800	[thread overview]
Message-ID: <49A88883.8090106@Sun.COM> (raw)
In-Reply-To: <4FA716B1526C7C4DB0375C6DADBC4EA34172695B6F@LONPMAILBOX01.citrite.net>


[-- Attachment #1.1: Type: text/plain, Size: 1238 bytes --]

On 02/27/09 16:03, Ian Pratt wrote:
>>> I found some posts from quite a while ago on xen-devel discussing
>>> patches to allow large pages, so my question is for clarification  on
>>> the status of this feature. I.e., is it in any stable release and if
>>> so what version?
>>>       
>> Its a work in progress, but there's nothing usable yet, as far as I
>> know.
>>     
>
> Oracle have been working on PV 2MB page support, and I expect they'll pitch in with an update.
>
> Over the last 18 months or so there have been a number of changes to xen's PV PT handling that make support of 2MB pages significantly easier than it was previously. However, the guest has to be careful how it uses them as it can't alias any memory that may be used for storing pagetables pages (that must be RO).
>
>   
Thanks for the update. I'll wait to hear from the Oracle guys.

You remark about aliasing prompts me to ask a general question about 
that. I am currently mapping physical to virtual 1-1 (because that is 
what minis-os has always done) as well as mapping parts of that to other 
areas in virtual memory. Both of these are RW mappings. Is that ok? It 
perfectly possible for me to unmap the 1-1 mappings or make them RO if I 
have to.

Mick


[-- Attachment #1.2: Type: text/html, Size: 1740 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2009-02-28  0:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27 23:01 2MB page PV guest support clarification Mick Jordan
2009-02-27 23:28 ` Jeremy Fitzhardinge
2009-02-27 23:54   ` Mick Jordan
2009-02-28  0:03   ` Ian Pratt
2009-02-28  0:42     ` Mick Jordan [this message]
2009-02-28  1:28       ` Ian Pratt
2009-02-28  1:37         ` Mick Jordan
2009-03-02 10:44           ` Rolf Neugebauer
2009-02-28 11:12     ` Keir Fraser
2009-03-02 13:45       ` Dave McCracken
2009-03-02 16:38         ` Mick Jordan
2009-03-02 16:23       ` Mick Jordan
2009-03-02 16:34         ` Keir Fraser

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=49A88883.8090106@Sun.COM \
    --to=mick.jordan@sun.com \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=jeremy@goop.org \
    --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.