From: Keir Fraser <keir@xen.org>
To: AP <apxeng@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: hap_2mb and hap_1gb options
Date: Thu, 08 Mar 2012 21:44:13 +0000 [thread overview]
Message-ID: <CB7ED8AD.3B268%keir@xen.org> (raw)
In-Reply-To: <CAGU+auvgfhSwB=zn7+uATM_7JHc2hqxTiTHXSkS=+BkafNRMTg@mail.gmail.com>
On 08/03/2012 19:38, "AP" <apxeng@gmail.com> wrote:
> On Thu, Mar 8, 2012 at 1:47 AM, Keir Fraser <keir@xen.org> wrote:
>> On 08/03/2012 06:11, "Keir Fraser" <keir.xen@gmail.com> wrote:
>>
>>>> Have I added the options in the right place? Do I need to do anything
>>>> else to disable super pages?
>>>
>>> Unfortunately there is no logging output that indicates that the
>>> hap_2mb/hap_1gb=0 options are working. You have set the options correctly.
>>>
>>> I will sort out a small patch for this.
>>
>> Done as xen_unstable:24992. I removed the VMX-specific "EPT supports XX
>> super page" lines, and replaced with a single line of the form (for
>> example):
>> HVM: HAP page sizes: 4kB, 2MB [disabled], 1GB [disabled]
>>
>> The '[disabled]' bit corresponds to setting hap_2mb/1gb=0.
>
> Thank you. This is very helpful. I realize that this is just an info
> output patch albeit a useful one. So any chance of having this
> considered for a backport to Xen 4.1.x?
Yes, should be easy to do.
-- Keir
> AP
>
>> -- Keir
>>
>>> -- Keir
>>>
>>>> Thanks,
>>>> AP
>>>>
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xen.org
>>>> http://lists.xen.org/xen-devel
>>>
>>>
>>
>>
next prev parent reply other threads:[~2012-03-08 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 0:36 hap_2mb and hap_1gb options AP
2012-03-08 6:11 ` Keir Fraser
2012-03-08 9:47 ` Keir Fraser
2012-03-08 19:38 ` AP
2012-03-08 21:44 ` Keir Fraser [this message]
2012-03-09 10:03 ` 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=CB7ED8AD.3B268%keir@xen.org \
--to=keir@xen.org \
--cc=apxeng@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).