From: "Jan Beulich" <JBeulich@suse.com>
To: Liang Z Li <liang.z.li@intel.com>
Cc: "tim@xen.org" <tim@xen.org>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>,
"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Yang Z Zhang <yang.z.zhang@intel.com>
Subject: Re: [v3] libxc: Expose the 1GB pages cpuid flag to guest
Date: Fri, 28 Nov 2014 10:39:22 +0000 [thread overview]
Message-ID: <54785EEA020000780004B5C7@mail.emea.novell.com> (raw)
In-Reply-To: <F2CBF3009FA73547804AE4C663CAB28E44FCBD@shsmsx102.ccr.corp.intel.com>
>>> On 28.11.14 at 11:29, <liang.z.li@intel.com> wrote:
>> > - if (!hvm_pse1gb_supported(d))
>>> + if (!hvm_pse1gb_supported(d) || paging_mode_shadow(d))
>>> *edx &= ~cpufeat_mask(X86_FEATURE_PAGE1GB);
>>
>>With
>>
>>#define hvm_pse1gb_supported(d) \
>> (cpu_has_page1gb && paging_mode_hap(d))
>
>>the change above is pointless. While, considering this, comments on
>>v2 may have been misleading, you should have simply updated the patch
> description instead to clarify why the v2 change was okay even for the shadow
> mode case.
>
> I checked the code and found that for a normal guest can only be in hap mode
> or shadow mode before I sending the patch, but I am not share if it's true
> for dom0.
The CPUID code in libxc doesn't apply to Dom0 at all, and CPUID
handling is also special cased in the hypervisor for Dom0. Plus
finally Dom0 only possibly being PV or PVH, PVH requiring HAP
and PV generally not allowing large pages anyway, your concern
is unnecessary.
Jan
prev parent reply other threads:[~2014-11-28 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 3:28 [v3] libxc: Expose the 1GB pages cpuid flag to guest Liang Li
2014-11-28 9:16 ` Jan Beulich
2014-11-28 10:29 ` Li, Liang Z
2014-11-28 10:32 ` Andrew Cooper
2014-11-28 10:38 ` Li, Liang Z
2014-11-28 10:39 ` Jan Beulich [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=54785EEA020000780004B5C7@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=liang.z.li@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.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.