From: Ingo Molnar <mingo@kernel.org>
To: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@suse.de>,
Andy Lutomirski <luto@kernel.org>,
Tony Luck <tony.luck@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Ravi V. Shankar" <ravi.v.shankar@intel.com>,
x86@kernel.org, ricardo.neri@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] x86/umip: Identify the str and sldt instructions
Date: Tue, 14 Nov 2017 08:20:23 +0100 [thread overview]
Message-ID: <20171114072023.wefilw2d7ym2bdft@gmail.com> (raw)
In-Reply-To: <20171114022647.GA1444@voyager>
* Ricardo Neri <ricardo.neri-calderon@linux.intel.com> wrote:
> On Mon, Nov 13, 2017 at 09:12:03AM +0100, Ingo Molnar wrote:
> >
> > * Ricardo Neri <ricardo.neri-calderon@linux.intel.com> wrote:
> >
> > > The instructions str and sldt are not emulated in any case. Thus, it made
> > > sense to not implement functionality to identify them. However, a
> > > subsequent commit will introduce functionality to warn about the use of
> > > all the instructions that UMIP protect, not only those that are emulated.
> > > A first step for that is the ability to identify them.
> > >
> > > Plus, now that str and sldt are identified, we need to explicitly avoid
> > > their emulation (i.e., not rely on unsuccessful identification). Group
> > > togehter all the cases that we do not want to emulate: str, sldt and user
> > > long mode processes.
> >
> > Did you notice how in all your previous patches (both in the code and in the
> > changelogs) I have manually fixed up the capitalization of these instruction
> > mnenonics?
>
> I am sorry, I tried to see where you made these changes but I could not find
> any. I did a git diff of arch/x86/kernel/umip.c between the branch rneri/umip_v11
> of my repository [1] and the master branch of the tip tree and I did not find
> any differences.
For example, I turned:
[PATCH v11 12/12] selftests/x86: Add tests for instruction str and sldt
The instructions str and sldt are not valid when running on virtual-8086
mode and generate an invalid operand exception.
...
into:
a9e017d5619e: selftests/x86: Add tests for the STR and SLDT instructions
The STR and SLDT instructions are not valid when running on virtual-8086
mode and generate an invalid operand exception.
...
I did not catch every case though.
Thanks,
Ingo
next prev parent reply other threads:[~2017-11-14 7:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 2:56 [PATCH 0/4] x86: Tweaks for UMIP Ricardo Neri
2017-11-13 2:56 ` [PATCH 1/4] x86/umip: Select X86_INTEL_UMIP by default Ricardo Neri
2017-11-13 2:56 ` [PATCH 2/4] x86/umip: Inform that UMIP has been enabled Ricardo Neri
2017-11-13 2:56 ` [PATCH 3/4] x86/umip: Identify the str and sldt instructions Ricardo Neri
2017-11-13 8:12 ` Ingo Molnar
2017-11-14 2:26 ` Ricardo Neri
2017-11-14 7:20 ` Ingo Molnar [this message]
2017-11-13 2:56 ` [PATCH 4/4] x86/umip: Warn if UMIP-protected instructions are used Ricardo Neri
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=20171114072023.wefilw2d7ym2bdft@gmail.com \
--to=mingo@kernel.org \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=pbonzini@redhat.com \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=ricardo.neri@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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