From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
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,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Lutomirski <luto@kernel.org>
Subject: [PATCH v2 0/2] x86/msr: MSR access failure changes
Date: Sun, 20 Sep 2015 17:02:54 -0700 [thread overview]
Message-ID: <cover.1442793572.git.luto@kernel.org> (raw)
This applies on top of my earlier paravirt MSR series.
Changes from v1:
- Return zero instead of poison on bad RDMSRs.
Andy Lutomirski (2):
x86/msr: Carry on after a non-"safe" MSR access fails without
!panic_on_oops
x86/msr: Set the return value to zero when native_rdmsr_safe fails
arch/x86/include/asm/msr.h | 5 ++++-
arch/x86/kernel/traps.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 59 insertions(+), 1 deletion(-)
--
2.4.3
next reply other threads:[~2015-09-21 0:02 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 0:02 Andy Lutomirski [this message]
2015-09-21 0:02 ` [PATCH v2 1/2] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops Andy Lutomirski
2015-09-21 0:02 ` Andy Lutomirski
2015-09-21 0:15 ` Linus Torvalds
2015-09-21 1:13 ` Andy Lutomirski
2015-09-21 8:46 ` Ingo Molnar
2015-09-21 8:46 ` Ingo Molnar
2015-09-21 12:27 ` Paolo Bonzini
2015-09-21 12:27 ` Paolo Bonzini
2015-09-21 16:36 ` Linus Torvalds
2015-09-21 16:36 ` Linus Torvalds
2015-09-21 16:49 ` Arjan van de Ven
2015-09-21 17:27 ` Linus Torvalds
2015-09-21 17:27 ` Linus Torvalds
2015-09-21 17:43 ` Andy Lutomirski
2015-09-22 8:12 ` Paolo Bonzini
2015-09-22 8:12 ` Paolo Bonzini
2015-09-21 17:43 ` Andy Lutomirski
2015-09-21 16:49 ` Arjan van de Ven
2015-09-21 18:16 ` Andy Lutomirski
2015-09-21 18:36 ` Borislav Petkov
2015-09-21 18:36 ` Borislav Petkov
2015-09-21 18:47 ` Linus Torvalds
2015-09-21 18:47 ` Linus Torvalds
2015-09-21 18:16 ` Andy Lutomirski
2015-09-22 7:14 ` Ingo Molnar
2015-09-22 7:14 ` Ingo Molnar
2015-09-30 13:10 ` Peter Zijlstra
2015-09-30 13:10 ` Peter Zijlstra
2015-09-30 14:01 ` Ingo Molnar
2015-09-30 18:04 ` Andy Lutomirski
2015-09-30 18:04 ` Andy Lutomirski
2015-10-01 7:15 ` Ingo Molnar
2015-10-01 7:15 ` Ingo Molnar
2016-03-11 16:48 ` Andy Lutomirski
2016-03-11 16:48 ` Andy Lutomirski
2016-03-12 16:02 ` Ingo Molnar
2016-03-12 16:02 ` Ingo Molnar
2015-09-30 14:01 ` Ingo Molnar
2015-09-30 18:32 ` H. Peter Anvin
2015-09-30 18:32 ` H. Peter Anvin
2015-09-21 1:13 ` Andy Lutomirski
2015-09-21 0:15 ` Linus Torvalds
2015-09-21 0:02 ` [PATCH v2 2/2] x86/msr: Set the return value to zero when native_rdmsr_safe fails Andy Lutomirski
2015-09-21 0:02 ` Andy Lutomirski
-- strict thread matches above, loose matches on Subject: below --
2015-09-21 0:02 [PATCH v2 0/2] x86/msr: MSR access failure changes 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=cover.1442793572.git.luto@kernel.org \
--to=luto@kernel.org \
--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=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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.