Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1356464

Re: [PATCH v2 1/2] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops

Path csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news2.arglkargh.de!news.mixmin.net!aioe.org!gothmog.csi.it!bofh.it!news.nic.it!robomod
From Ingo Molnar <mingo@kernel.org>
Newsgroups linux.kernel
Subject Re: [PATCH v2 1/2] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops
Date Sat, 12 Mar 2016 17:10:02 +0100
Message-ID <rbUh4-gw-23@gated-at.bofh.it> (permalink)
References <qaWQ9-6YN-7@gated-at.bofh.it> <qaWZP-79N-1@gated-at.bofh.it> <qaXVT-8u0-1@gated-at.bofh.it> <qb4Xo-1x9-9@gated-at.bofh.it> <qbcid-3Gm-5@gated-at.bofh.it> <qepsC-63w-17@gated-at.bofh.it> <qeqf0-7dN-19@gated-at.bofh.it> <qetZf-4bK-15@gated-at.bofh.it> <qeGjM-58Q-21@gated-at.bofh.it> <rbyqd-CG-5@gated-at.bofh.it>
X-Original-To Andy Lutomirski <luto@amacapital.net>
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=/SmEikAQg9A9yYYsXVkRfuteesxteao2BZP8N7TwoGk=; b=T/qbM6rrCZa5Q+e1vgA8YRPr8+Dl/Vqg2PN1C03JdRFoUpPPNfHvIVLihabYCQ/GgW V2jTTFVZK0wtUIRvkfJMqLeecaaDXL8zNRbVZ9+KCbX4H96rs6vsxAa2I1eAEFt/HonT VjmD2IXF6mBuFbczf1fM/6V5BoYMXsd8Q54HT7iUgXZIdQK+BOycq5/mFz20yO0dXdLZ 26b6Am3INsVV2tieOsGq/mv8dD5vBWKKkOInuyJY8HZyN4S76JYYLXLnTzz4+Pc7bXWq Cwb3c/joSdJXXAZWYw2tmvwYRthkUG4YO01KS5iGqkwo2EearJT8oGuaPaL72aKtmTft PwvA==
X-Google-Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=/SmEikAQg9A9yYYsXVkRfuteesxteao2BZP8N7TwoGk=; b=YQ1CXh8LSmuZyEATM/NVC0ZPGcX4Q4PNy8TXwBVkukjFqVRD5d2/wenL6OgO3cst4e URtkZu1UQmCqNiKhQ+8qfO5mq9rRBjYXyix77isXSpjtddhuHZGSZa2ysTx/TpmR1hMK j5QgojjqEmg78A+W1ScXPuHd/YKHXIGK/TY8yN9dWk75glZSz+yH6ZgX201jvGFTOYsK VxBOI5cfCIQR02Dm1ph6sfRC6rvrm7ieeCIZPD43lr8ZzVZB8Yg36uW22i9PiO0F37Dj 1lMDd9kgQrmUwLlqUyCPHGssollp/RP8t5uTBECMGZ/k+apiq/6EgH3/uACJukU4Mwdc z+yw==
X-Gm-Message-State AD7BkJLOqnY5vHYmlsjLrum21YLUZGDpZSL6BB2tpLvlkDucEN0Y3+G1xPIW1K0KMvs+bg==
X-Received by 10.28.47.216 with SMTP id v207mr8925255wmv.7.1457798564919; Sat, 12 Mar 2016 08:02:44 -0800 (PST)
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Disposition inline
User-Agent Mutt/1.5.23 (2014-03-12)
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 37
Organization linux.* mail to news gateway
X-Original-Cc Peter Zijlstra <peterz@infradead.org>, Linus Torvalds <torvalds@linux-foundation.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>
X-Original-Date Sat, 12 Mar 2016 17:02:42 +0100
X-Original-Message-ID <20160312160241.GA11531@gmail.com>
X-Original-References <130a3b7ef4788baae3a6fe71293ab17442bc9a0a.1442793572.git.luto@kernel.org> <CA+55aFy4Chd-PJvxGne=TztPsvFqUG07Ht8mtc4+0oGNZNDOyw@mail.gmail.com> <CALCETrXqsKcqzfqMO2ctOJJ4X8Kb6vvoUpVDir9F2-a3XwK23w@mail.gmail.com> <20150921084642.GA30984@gmail.com> <CA+55aFzKCi6pf0RP8HjDQYDsms6reB5AihuCAHEkVJtoOHk_Yw@mail.gmail.com> <20150930131002.GK2881@worktop.programming.kicks-ass.net> <20150930140122.GB3285@gmail.com> <CALCETrVMV2_3ywQ_t+0rsqzxMm6D9PvDEmOdrie67rRzfj-W_Q@mail.gmail.com> <20151001071505.GA21542@gmail.com> <CALCETrUFakwGL9zpj9TwKX9KbG9czq8fpEViU3nWaCvnpGurew@mail.gmail.com>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1356464

Show key headers only | View raw


* Andy Lutomirski <luto@amacapital.net> wrote:

> On Thu, Oct 1, 2015 at 12:15 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > * Andy Lutomirski <luto@amacapital.net> wrote:
> >
> >> > These could still be open coded in an inlined fashion, like the scheduler usage.
> >>
> >> We could have a raw_rdmsr for those.
> >>
> >> OTOH, I'm still not 100% convinced that this warn-but-don't-die behavior is
> >> worth the effort.  This isn't a frequent source of bugs to my knowledge, and we
> >> don't try to recover from incorrect cr writes, out-of-bounds MMIO, etc, so do we
> >> really gain much by rigging a recovery mechanism for rdmsr and wrmsr failures
> >> for code that doesn't use the _safe variants?
> >
> > It's just the general principle really: don't crash the kernel on bootup. There's
> > few things more user hostile than that.
> >
> > Also, this would maintain the status quo: since we now (accidentally) don't crash
> > the kernel on distro kernels (but silently and unsafely ignore the faulting
> > instruction), we should not regress that behavior (by adding the chance to crash
> > again), but improve upon it.
> 
> Just a heads up: the extable improvements in tip:ras/core make it
> straightforward to get the best of all worlds: explicit failure
> handling (written in C!), no fast path overhead whatsoever, and no new
> garbage in the exception handlers.

I _knew_ I should have merged them into tip:x86/mm, not tip:ras/core ;-)

I had a quick look at your new MSR series and I'm very happy with that direction!

Thanks,

	Ingo

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Re: [PATCH v2 1/2] x86/msr: Carry on after a non-"safe" MSR access  fails without !panic_on_oops Andy Lutomirski <luto@amacapital.net> - 2016-03-11 17:50 +0100
  Re: [PATCH v2 1/2] x86/msr: Carry on after a non-"safe" MSR access  fails without !panic_on_oops Ingo Molnar <mingo@kernel.org> - 2016-03-12 17:10 +0100

csiph-web