From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xenproject.org, ian.jackson@eu.citrix.com,
stefano.stabellini@eu.citrix.com, ian.campbell@citrix.com,
jun.nakajima@intel.com
Subject: 1GB hugepages and intel_xc_cpuid_policy by default disables it.
Date: Fri, 10 Jan 2014 13:41:52 -0500 [thread overview]
Message-ID: <20140110184151.GA20232@pegasus.dumpdata.com> (raw)
Hey,
It occured to me that when booting Linux HVM guests, the 1GB hugepage
cpuid is not exposed. One needs to manually do:
cpuid= ['0x80000001:edx=xxxxx1xxxxxxxxxxxxxxxxxxxxxxxxxx']
or
cpuid="host,page1gb=k"
(see http://lists.xenproject.org/archives/html/xen-users/2013-09/msg00083.html
for some discussion about it).
The machine I am using is supporting it:
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
and this is the only way to get hugepages working
(for reference here is what I have in the guest command line:
"default_hugepagesz=1G hugepagesz=1G hugepages=2 hugepagesz=2M
hugepages=100" and without this cpuid I get:
hugepagesz: Unsupported page size 1024 M
because the 1GB flag is not exposed.
I was wondering why we don't check the host cpuid and set the 1GB
flag (pdpe1gb) for those cases? It seems that all the pieces are in
place for this to work?
Thanks!
next reply other threads:[~2014-01-10 18:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 18:41 Konrad Rzeszutek Wilk [this message]
2014-01-13 10:10 ` 1GB hugepages and intel_xc_cpuid_policy by default disables it Ian Campbell
2014-01-13 11:30 ` Jan Beulich
2014-01-13 11:38 ` Ian Campbell
2014-01-13 11:51 ` Jan Beulich
2014-01-15 20:07 ` Konrad Rzeszutek Wilk
2014-01-16 7:49 ` Jan Beulich
2014-11-10 5:08 ` Zhang, Yang Z
2014-11-10 14:57 ` Konrad Rzeszutek Wilk
2014-11-11 3:30 ` Zhang, Yang Z
2014-11-11 15:45 ` Konrad Rzeszutek Wilk
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=20140110184151.GA20232@pegasus.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jun.nakajima@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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.