From: Sheng Yang <sheng@linux.intel.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 2/4] KVM: Extended shared_msr_global to per CPU
Date: Thu, 17 Dec 2009 23:01:32 +0800 [thread overview]
Message-ID: <200912172301.33033.sheng@linux.intel.com> (raw)
In-Reply-To: <4B2A08A8.7080603@redhat.com>
On Thursday 17 December 2009 18:32:08 Avi Kivity wrote:
> On 12/17/2009 11:32 AM, Sheng Yang wrote:
> > shared_msr_global saved host value of relevant MSRs, but it have an
> > assumption that all MSRs it tracked shared the value across the different
> > CPUs. It's not true with some MSRs, e.g. MSR_TSC_AUX.
> >
> > Extend it to per CPU to provide the support of MSR_TSC_AUX, and more
> > alike MSRs.
> >
> > Notice now the shared_msr_global still have one assumption: it can only
> > deal with the MSRs that won't change in host after KVM module loaded.
> >
> > Signed-off-by: Sheng Yang<sheng@linux.intel.com>
> > ---
> >
> > How about this?
> >
> > Move the all initialization to hardware_enable(). And only initialized
> > once for each cpu.
> >
> >
> > -void kvm_define_shared_msr(unsigned slot, u32 msr)
> > +static void shared_msr_update(unsigned slot, u32 msr)
> > {
> > - int cpu;
> > + struct kvm_shared_msrs *smsr;
> > u64 value;
> >
> > + smsr =&__get_cpu_var(shared_msrs);
> > + /* only read, and nobody should modify it at this time,
> > + * so don't need lock */
> > + if (slot>= shared_msrs_global.nr) {
> > + printk(KERN_ERR "kvm: invalid MSR slot!");
> > + return;
> > + }
> > + if (smsr->values[slot].initialized)
> > + return;
>
> I don't think .initialized is worthwhile. shared_msr_update is run very
> rarely.
The reason is, after cpu hotplug, the MSR_TSC_AUX would be rewritten by
vsyscall_init again. But in the hotplug notifier chain, KVM has higher
priority(20 vs 0 for vsyscall_init), so maybe the rdmsr() here would get a
bogus value... Then I think prevent it from initializing again should be
safer.
But I just think of another issue: if we hot plug in a cpu(without hot plug
off), it would have a bogus value as well in the same path? Sound
troublesome...
>
> > + smsr->values[slot].initialized = true;
> > + put_cpu_var(shared_msrs);
>
> If you use __get_cpu_var(), you need to remove put_cpu_var().
>
Sure...
--
regards
Yang, Sheng
next prev parent reply other threads:[~2009-12-17 15:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 5:48 [PATCH 0/4] Add support for RDTSCP in VMX Sheng Yang
2009-12-16 5:48 ` [PATCH 1/4] KVM: VMX: Remove redundant variable Sheng Yang
2009-12-16 5:48 ` [PATCH 2/4] KVM: Extended shared_msr_global to per CPU Sheng Yang
2009-12-16 9:21 ` Avi Kivity
2009-12-17 9:32 ` Sheng Yang
2009-12-17 10:32 ` Avi Kivity
2009-12-17 15:01 ` Sheng Yang [this message]
2009-12-17 15:06 ` Avi Kivity
2009-12-16 5:48 ` [PATCH 3/4] x86: Add IA32_TSC_AUX MSR Sheng Yang
2009-12-16 5:48 ` [PATCH 4/4] KVM: VMX: Add instruction rdtscp support for guest Sheng Yang
2009-12-16 9:47 ` Avi Kivity
2009-12-17 9:33 ` Sheng Yang
2009-12-17 10:39 ` Avi Kivity
2009-12-17 14:52 ` Sheng Yang
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=200912172301.33033.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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).