[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrVKM=gH_FjTzv=Xg6YCF8Ax_WJ+0RU9Zr7rNtDjadEgAg@mail.gmail.com>
Date: Mon, 14 Mar 2016 09:53:34 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: xen-devel <Xen-devel@...ts.xen.org>,
Arjan van de Ven <arjan@...ux.intel.com>,
X86 ML <x86@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
KVM list <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v3 3/5] x86/paravirt: Add paravirt_{read,write}_msr
On Mar 14, 2016 7:03 AM, "Paolo Bonzini" <pbonzini@...hat.com> wrote:
>
>
>
> On 11/03/2016 20:06, Andy Lutomirski wrote:
> > This adds paravirt hooks for unsafe MSR access. On native, they
> > call native_{read,write}_msr. On Xen, they use
> > xen_{read,write}_msr_safe.
> >
> > Nothing uses them yet for ease of bisection. The next patch will
> > use them in rdmsrl, wrmsrl, etc.
> >
> > I intentionally didn't make them OOPS on #GP on Xen. I think that
> > should be done separately by the Xen maintainers.
>
> Please do the same for KVM.
Can you clarify? KVM uses the native version, and the native version
only oopses with this series applied if panic_on_oops is set.
--Andy
Powered by blists - more mailing lists