From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Li, Xin B" <xin.b.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH]Abstract vmcs feature detect part
Date: Thu, 26 Jul 2007 12:50:20 +0300 [thread overview]
Message-ID: <46A86E5C.9000106@qumranet.com> (raw)
In-Reply-To: <B30DA1341B0CFA4893EF8A36B40B5C5D016FE9D0-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Li, Xin B wrote:
>>> This patch replaces vmcs_write32_fixedbits() with
>>>
>> adjust_vmx_controls(),
>>
>> It still doesn't say why, but I can now see it: this is code
>>
> >from Xen. I have no objection to copying Xen code, but it needs to be
> documented in
>
>> the changelog, and there needs to be a good reason as to why you're
>> replacing existing code rather than improving it. So far I don't see
>> this reason
>>
>
> We want to enable MSR BITMAP and VTPR for VMX guest, which depend on
> this, I think you're already aware this.
> And another reason is, all physical CPUs on the system should support
> the _same_ VMX features set, or obviously it's weird that one CPU
> support Intel VTPR feature while some other not. This is a rare case,
> but basically we should detect it when KVM is being initialized, and
> this patch also helps.
>
>
Sure. Please update the changelog to state this.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-07-26 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 10:17 [PATCH]Abstract vmcs feature detect part Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557F5E9F47-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-26 5:20 ` Avi Kivity
[not found] ` <46A82F11.4030100-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-26 6:12 ` Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557F5EA1CC-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-26 8:24 ` Avi Kivity
[not found] ` <46A85A35.7040902-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-26 8:57 ` Li, Xin B
[not found] ` <B30DA1341B0CFA4893EF8A36B40B5C5D016FE9D0-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-26 9:01 ` Li, Xin B
[not found] ` <B30DA1341B0CFA4893EF8A36B40B5C5D016FE9D8-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-26 9:49 ` Avi Kivity
2007-07-26 9:50 ` Avi Kivity [this message]
[not found] ` <46A86E5C.9000106-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-27 5:24 ` Yang, Sheng
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=46A86E5C.9000106@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=xin.b.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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.