From: Andy Lutomirski <luto@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH] x86/traps: Have read_cr0() only once in the #NM handler
Date: Thu, 17 Jan 2019 11:24:17 -0800 [thread overview]
Message-ID: <CALCETrUbiuYoDzLcHm+pXYyVJWcffiY76eu6UxuaDxtOk765pw@mail.gmail.com> (raw)
In-Reply-To: <20190117120728.3811-1-bp@alien8.de>
On Thu, Jan 17, 2019 at 4:07 AM Borislav Petkov <bp@alien8.de> wrote:
>
> From: Borislav Petkov <bp@suse.de>
>
> ... instead of twice in the code. In any case, CR0 ends up being read
> once anyway:
>
> 1. The CONFIG_MATH_EMULATION case does so and exits.
> 2. The normal case does it once too.
>
Reviewed-by: Andy Lutomirski <luto@kernel.org>
next prev parent reply other threads:[~2019-01-17 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 12:07 [PATCH] x86/traps: Have read_cr0() only once in the #NM handler Borislav Petkov
2019-01-17 12:14 ` Sebastian Andrzej Siewior
2019-01-17 19:24 ` Andy Lutomirski [this message]
2019-01-22 13:30 ` [tip:x86/fpu] " tip-bot for Borislav Petkov
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=CALCETrUbiuYoDzLcHm+pXYyVJWcffiY76eu6UxuaDxtOk765pw@mail.gmail.com \
--to=luto@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).