[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrW9EYi5dzCKNtKkxM18CC4n5BZxTp1=qQ5qZccwstXjzg@mail.gmail.com>
Date: Thu, 19 Mar 2020 08:44:03 -0700
From: Andy Lutomirski <luto@...nel.org>
To: Joerg Roedel <joro@...tes.org>
Cc: X86 ML <x86@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
Andy Lutomirski <luto@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Hellstrom <thellstrom@...are.com>,
Jiri Slaby <jslaby@...e.cz>,
Dan Williams <dan.j.williams@...el.com>,
Tom Lendacky <thomas.lendacky@....com>,
Juergen Gross <jgross@...e.com>,
Kees Cook <keescook@...omium.org>,
LKML <linux-kernel@...r.kernel.org>,
kvm list <kvm@...r.kernel.org>,
Linux Virtualization <virtualization@...ts.linux-foundation.org>,
Joerg Roedel <jroedel@...e.de>
Subject: Re: [PATCH 41/70] x86/sev-es: Add Runtime #VC Exception Handler
On Thu, Mar 19, 2020 at 2:14 AM Joerg Roedel <joro@...tes.org> wrote:
>
> From: Tom Lendacky <thomas.lendacky@....com>
>
> Add the handler for #VC exceptions invoked at runtime.
If I read this correctly, this does not use IST. If that's true, I
don't see how this can possibly work. There at least two nasty cases
that come to mind:
1. SYSCALL followed by NMI. The NMI IRET hack gets to #VC and we
explode. This is fixable by getting rid of the NMI EFLAGS.TF hack.
2. tools/testing/selftests/x86/mov_ss_trap_64. User code does MOV
(addr), SS; SYSCALL, where addr has a data breakpoint. We get #DB
promoted to #VC with no stack.
Powered by blists - more mailing lists