From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Paolo Bonzini <pbonzini@redhat.com>,
xen-devel <Xen-devel@lists.xen.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
KVM list <kvm@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2 1/2] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops
Date: Mon, 21 Sep 2015 20:36:34 +0200 [thread overview]
Message-ID: <20150921183634.GE3666@pd.tnic> (raw)
In-Reply-To: <CALCETrUBcDxvtjKC-m97GPwCOHvcoDdGjnMJLukSue8ha55mng@mail.gmail.com>
On Mon, Sep 21, 2015 at 11:16:30AM -0700, Andy Lutomirski wrote:
> In the interest of sanity, I want to drop the "native_", too, since
> there appear to be few or no good use cases for native_read_msr as
> such. I'm tempted to add new functions read_msr and write_msr that
> forward to rdmsrl_safe and wrmsrl_safe.
Just change the msr_read/msr_write() ones in arch/x86/lib/msr.c to take
a u64 and you're there.
> It looks like the msr helpers are every bit as bad as the TSC helpers
> used to be :(
Yap.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2015-09-21 18:36 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 0:02 [PATCH v2 0/2] x86/msr: MSR access failure changes Andy Lutomirski
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 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 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-21 17:43 ` Andy Lutomirski
2015-09-22 8:12 ` Paolo Bonzini
2015-09-22 8:12 ` Paolo Bonzini
2015-09-21 18:16 ` Andy Lutomirski
2015-09-21 18:36 ` Borislav Petkov
2015-09-21 18:36 ` Borislav Petkov [this message]
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 14:01 ` Ingo Molnar
2015-09-30 14:01 ` Ingo Molnar
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-12 16:02 ` Ingo Molnar
2016-03-12 16:02 ` Ingo Molnar
2016-03-11 16:48 ` Andy Lutomirski
2015-09-30 18:04 ` Andy Lutomirski
2015-09-30 13:10 ` Peter Zijlstra
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: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
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=20150921183634.GE3666@pd.tnic \
--to=bp@alien8.de \
--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@amacapital.net \
--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.