On Wed, Jul 09, 2014 at 02:32:28PM +0000, Liang, Kan wrote:
>
>
> > On Tue, Jul 08, 2014 at 09:49:40AM -0700, kan.li...@intel.com wrote:
> > > +/*
> > > + * Under certain circumstances, access certain MSR may cause #GP.
> > > + * The function tests if the input MSR can be safely accessed.
> > > + */
> > > +static inline bool check_msr(unsigned long msr) {
> > > + u64 value;
> > > +
> > > + if (rdmsrl_safe(msr, &value) < 0)
> > > + return false;
> > > + if (wrmsrl_safe(msr, value) < 0)
> > > + return false;
> > > + return true;
> > > +}
> >
> > What does this thing return after patch 2? does the write still fault or
> > will
> > KVM silently take writes too?
>
> If applying patch 2, the function will return true. The KVM just simply
> ignore the reads/writes.OK, then that's broken too. We want a function to return false for any malfunctioning MSR, ignoring writes and returning 0s is not proper functioning.
pgpw9EoY9DQwh.pgp
Description: PGP signature
