From: Paolo Bonzini <pbonzini@redhat.com>
To: Andy Lutomirski <luto@kernel.org>, X86 ML <x86@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
KVM list <kvm@vger.kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>,
xen-devel <Xen-devel@lists.xen.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v3 3/5] x86/paravirt: Add paravirt_{read,write}_msr
Date: Mon, 14 Mar 2016 15:02:58 +0100 [thread overview]
Message-ID: <56E6C492.5060308@redhat.com> (raw)
In-Reply-To: <c7fb2aafd8a5885e9c333957abef9e29b691098e.1457723023.git.luto@kernel.org>
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.
Paolo
next prev parent reply other threads:[~2016-03-14 14:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 19:06 [PATCH v3 0/5] Improve non-"safe" MSR access failure handling Andy Lutomirski
2016-03-11 19:06 ` [PATCH v3 1/5] x86/paravirt: Add _safe to the read_msr and write_msr PV hooks Andy Lutomirski
2016-03-11 19:06 ` Andy Lutomirski
2016-03-11 19:06 ` [PATCH v3 2/5] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops Andy Lutomirski
2016-03-11 19:06 ` Andy Lutomirski
2016-03-12 15:31 ` Ingo Molnar
2016-03-12 15:31 ` Ingo Molnar
2016-03-12 15:36 ` Ingo Molnar
2016-03-12 17:32 ` Andy Lutomirski
2016-03-12 17:32 ` Andy Lutomirski
2016-03-12 15:36 ` Ingo Molnar
2016-03-11 19:06 ` [PATCH v3 3/5] x86/paravirt: Add paravirt_{read,write}_msr Andy Lutomirski
2016-03-14 14:02 ` Paolo Bonzini [this message]
2016-03-14 16:53 ` [PATCH v3 3/5] x86/paravirt: Add paravirt_{read, write}_msr Andy Lutomirski
2016-03-14 16:53 ` [PATCH v3 3/5] x86/paravirt: Add paravirt_{read,write}_msr Andy Lutomirski
2016-03-14 16:58 ` [PATCH v3 3/5] x86/paravirt: Add paravirt_{read, write}_msr Linus Torvalds
2016-03-14 17:02 ` Andy Lutomirski
2016-03-14 17:02 ` [PATCH v3 3/5] x86/paravirt: Add paravirt_{read,write}_msr Andy Lutomirski
2016-03-15 8:49 ` Paolo Bonzini
2016-03-15 8:49 ` [PATCH v3 3/5] x86/paravirt: Add paravirt_{read, write}_msr Paolo Bonzini
2016-03-15 8:56 ` [PATCH v3 3/5] x86/paravirt: Add paravirt_{read,write}_msr Paolo Bonzini
2016-03-15 8:56 ` [PATCH v3 3/5] x86/paravirt: Add paravirt_{read, write}_msr Paolo Bonzini
2016-03-14 14:02 ` Paolo Bonzini
2016-03-11 19:06 ` Andy Lutomirski
2016-03-11 19:06 ` [PATCH v3 4/5] x86/paravirt: Make "unsafe" MSR accesses unsafe even if PARAVIRT=y Andy Lutomirski
2016-03-11 19:06 ` Andy Lutomirski
2016-03-11 19:06 ` [PATCH v3 5/5] x86/msr: Set the return value to zero when native_rdmsr_safe fails Andy Lutomirski
2016-03-11 19:06 ` Andy Lutomirski
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=56E6C492.5060308@redhat.com \
--to=pbonzini@redhat.com \
--cc=Xen-devel@lists.xen.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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.