From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: Dave McCracken <dcm@mccr.org>, xen-devel@lists.xensource.com
Subject: Re: [PATCH 0/2] Add hugetlb support for PV
Date: Thu, 24 Jul 2008 07:50:10 -0700 [thread overview]
Message-ID: <488896A2.3010500@goop.org> (raw)
In-Reply-To: <4888AC8E.76E4.0078.0@novell.com>
Jan Beulich wrote:
>>>> Dave McCracken <dcm@mccr.org> 24.07.08 15:45 >>>
>>>>
>> Here is a set of small patches that enables hugetlb on PV machines. They are
>> against xen-unstable and linux-2.6.18-xen.
>>
>> The patches are specifically for x86_64.
>>
>> I originally had these patches working back in May, but recently for some
>> reason my machine now refuses to boot the baseline xen-unstable, so I've been
>> unable to verify them. However, they should still work.
>>
>> Comments, bug reports, and suggestions are welcome.
>>
>
> I must be missing something, but I can't see how you guarantee the
> super pages to be contiguous in machine memory. And even if you did,
> the hypervisor would still need to do accounting on all the 4k portions
> a super page consists of when it gets mapped/unmapped.
>
Yeah, I'm pretty sure there has to be a lot more to it than that.
J
prev parent reply other threads:[~2008-07-24 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 13:45 [PATCH 0/2] Add hugetlb support for PV Dave McCracken
2008-07-24 13:48 ` [PATCH 1/2] PV Hugetlb support - Hypervisor portion Dave McCracken
2008-07-24 13:51 ` Dave McCracken
2008-07-24 13:50 ` [PATCH 2/2] PV hugetlb support - kernel portion Dave McCracken
2008-07-24 14:23 ` [PATCH 0/2] Add hugetlb support for PV Jan Beulich
2008-07-24 14:50 ` 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=488896A2.3010500@goop.org \
--to=jeremy@goop.org \
--cc=dcm@mccr.org \
--cc=jbeulich@novell.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.