[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3cdde8ac-500c-ddad-5ea5-a733e2c98d84@redhat.com>
Date: Wed, 8 Nov 2017 17:53:12 +0100
From: Denys Vlasenko <dvlasenk@...hat.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Paolo Bonzini <pbonzini@...hat.com>, Peter Anvin <hpa@...or.com>,
Borislav Petkov <bp@...e.de>, Vlastimil Babka <vbabka@...e.cz>,
Tony Luck <tony.luck@...el.com>,
Fenghua Yu <fenghua.yu@...el.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Borislav Petkov <bp@...en8.de>,
Brian Gerst <brgerst@...il.com>,
Jonathan Corbet <corbet@....net>,
"Ravi V. Shankar" <ravi.v.shankar@...el.com>,
ricardo.neri-calderon@...ux.intel.com,
Chris Metcalf <cmetcalf@...lanox.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Masami Hiramatsu <mhiramat@...nel.org>,
Andrew Lutomirski <luto@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>, ray.huang@....com,
"Michael S. Tsirkin" <mst@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Chen Yucong <slaoub@...il.com>, Ingo Molnar <mingo@...nel.org>,
Jiri Slaby <jslaby@...e.cz>, Shuah Khan <shuah@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"linux-tip-commits@...r.kernel.org"
<linux-tip-commits@...r.kernel.org>
Subject: Re: [tip:x86/asm] x86/umip: Add emulation code for UMIP instructions
On 11/08/2017 05:34 PM, Linus Torvalds wrote:
> On Wed, Nov 8, 2017 at 8:14 AM, Denys Vlasenko <dvlasenk@...hat.com> wrote:
>>
>> Can we avoid maintain emulation of these isns, by asking Wine to remove
>> their use instead?
>
> If we ask the Wine people to remove the instruction use, that may mean
> that we can avoid the emulation in four or five _years_ once everybody
> has updated.
>
> But it wouldn't mean that we could avoid it today.
We can postpone enabling UMIP by default by a year or so.
By this time, new Wine will be on majority of users' machines.
Then, when kernels switch to enable UMIP by default, umip=0
kernel flag can be used if somebody for some reason updates
their kernel but not Wine.
This is much less code, and simpler code, than implementing SIDT et al
emulation.
Keep in mind that our SIDT emulation itself can turn out to be buggy,
in the worst case it may end up having worse holes that
SIDT isns was - what if it can be tricked into writing into
arbitrary kernel address?
Powered by blists - more mailing lists