All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mick Jordan <Mick.Jordan@sun.com>
To: Dave McCracken <dcm@mccr.org>
Cc: Xen Developers List <xen-devel@lists.xensource.com>
Subject: Re: Design question for PV superpage support
Date: Mon, 02 Mar 2009 09:45:06 -0800	[thread overview]
Message-ID: <49AC1B22.50307@Sun.COM> (raw)
In-Reply-To: <49AC0C96.7070608@Sun.COM>

On 03/02/09 08:43, Mick Jordan wrote:
> On 03/02/09 05:54, Dave McCracken wrote:
>> The solution I am working on for how to support Linux hugepages (Xen 
>> superpages) involves creating domains made up entirely of 
>> superpages.  I can create a working domain with superpages and am in 
>> the process of supporting it in save/restore.
>>
>>   
I'm assuming that this means that everything is upgraded from 4K to 2MB. 
E.g. pfn 0 = 0, pfn 1 = 2MB., etc., and the mfn<->pfn maps also.
> This wouldn't work too well for me in the case of thread stacks 
> because we need to map out parts of the stack and, although we want 
> large virtual stacks, we don't want do dedicate that much physical 
> memory. Is it really difficult to support mixed pages sizes in the 
> general case, e.g., save/restore etc.?
Save/restore is definitely important for me and we do support it at 
present. I'm wondering if I might be able to "reapply" my 2MB mappings 
after a restore on a 4K system, given that these are just layered on a 
1-1 mapping between physical/virtual for all allocated memory.

Mick

  parent reply	other threads:[~2009-03-02 17:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 13:54 Design question for PV superpage support Dave McCracken
2009-03-02 13:58 ` Keir Fraser
2009-03-02 16:43 ` Mick Jordan
2009-03-02 17:06   ` Keir Fraser
2009-03-02 18:02     ` Mick Jordan
2009-03-02 17:29   ` Dave McCracken
2009-03-02 17:52     ` Keir Fraser
2009-03-02 18:03       ` Dan Magenheimer
2009-03-02 18:30         ` Keir Fraser
2009-03-02 18:46           ` Mick Jordan
2009-03-02 18:48           ` Dan Magenheimer
2009-03-02 19:04             ` Keir Fraser
2009-03-02 17:45   ` Mick Jordan [this message]
2009-03-02 17:54     ` Keir Fraser
2009-03-02 18:00     ` Dave McCracken
2009-03-02 18:14       ` Mick Jordan
2009-03-02 19:14         ` Dave McCracken
2009-03-03  1:37           ` Jeremy Fitzhardinge
2009-03-03  3:59             ` Mick Jordan
2009-03-03 14:33               ` Dan Magenheimer
2009-03-03 17:06                 ` Mick Jordan
2009-03-03 17:23                   ` Jeremy Fitzhardinge
2009-03-03 18:10                   ` Keir Fraser
2009-03-03 17:28                 ` Jeremy Fitzhardinge
2009-03-03 18:09                   ` Dan Magenheimer
2009-03-03 17:26               ` Jeremy Fitzhardinge
2009-03-03  1:32       ` Jeremy Fitzhardinge
2009-03-03  1:15 ` 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=49AC1B22.50307@Sun.COM \
    --to=mick.jordan@sun.com \
    --cc=dcm@mccr.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.