Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1236331
| 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 | 2015-09-30 16:10 +0200 |
| Message-ID | <qeqf0-7dN-19@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <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> |
| Organization | linux.* mail to news gateway |
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, Sep 21, 2015 at 09:36:15AM -0700, Linus Torvalds wrote:
> > On Mon, Sep 21, 2015 at 1:46 AM, Ingo Molnar <mingo@kernel.org> wrote:
> > >
> > > Linus, what's your preference?
> >
> > So quite frankly, is there any reason we don't just implement
> > native_read_msr() as just
> >
> > unsigned long long native_read_msr(unsigned int msr)
> > {
> > int err;
> > unsigned long long val;
> >
> > val = native_read_msr_safe(msr, &err);
> > WARN_ON_ONCE(err);
> > return val;
> > }
> >
> > Note: no inline, no nothing. Just put it in arch/x86/lib/msr.c, and be
> > done with it. I don't see the downside.
> >
> > How many msr reads are <i>so</i> critical that the function call
> > overhead would matter? Get rid of the inline version of the _safe()
> > thing too, and put that thing there too.
>
> There are a few in the perf code, and esp. on cores without a stack engine the
> call overhead is noticeable. Also note that the perf MSRs are generally
> optimized MSRs and less slow (we cannot say fast, they're still MSRs) than
> regular MSRs.
These could still be open coded in an inlined fashion, like the scheduler usage.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH v2 1/2] x86/msr: Carry on after a non-"safe" MSR access fails without !panic_on_oops Peter Zijlstra <peterz@infradead.org> - 2015-09-30 15:20 +0200
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> - 2015-09-30 16:10 +0200
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> - 2015-09-30 20:10 +0200
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> - 2015-10-01 09:20 +0200
csiph-web