[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1911122040020.1833@nanos.tec.linutronix.de>
Date: Tue, 12 Nov 2019 20:40:52 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Andy Lutomirski <luto@...nel.org>
cc: LKML <linux-kernel@...r.kernel.org>, X86 ML <x86@...nel.org>,
Linus Torvalds <torvalds@...uxfoundation.org>,
Stephen Hemminger <stephen@...workplumber.org>,
Willy Tarreau <w@....eu>, Juergen Gross <jgross@...e.com>,
Sean Christopherson <sean.j.christopherson@...el.com>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [patch V2 15/16] x86/iopl: Remove legacy IOPL option
On Tue, 12 Nov 2019, Andy Lutomirski wrote:
> On Mon, Nov 11, 2019 at 2:35 PM Thomas Gleixner <tglx@...utronix.de> wrote:
> >
> > From: Thomas Gleixner <tglx@...utronix.de>
> >
> > The IOPL emulation via the I/O bitmap is sufficient. Remove the legacy
> > cruft dealing with the (e)flags based IOPL mechanism.
>
> Acked-by: Andy Lutomirski <luto@...nel.org>
>
> But I think you could simplify a little bit and have a single config
> option that controls the iopl() and iopl() syscalls.
You mean turning off both iopl() and ioperm() in one go. Yes, that'd be
possible. Let me look.
Thanks,
tglx
Powered by blists - more mailing lists