From: Sean Christopherson <sean.j.christopherson@intel.com>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
X86 ML <x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Allison Randal <allison@lohutok.net>,
Enrico Weigelt <info@metux.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>,
Martin Molnar <martin.molnar.programming@gmail.com>,
Andy Lutomirski <luto@kernel.org>,
Alexandre Chartre <alexandre.chartre@oracle.com>,
Jann Horn <jannh@google.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] Fix undefined operation fault that can hang a cpu on crash or panic
Date: Tue, 7 Jul 2020 12:24:55 -0700 [thread overview]
Message-ID: <20200707192455.GI20096@linux.intel.com> (raw)
In-Reply-To: <1594148978.965916054@apps.rackspace.com>
On Tue, Jul 07, 2020 at 03:09:38PM -0400, David P. Reed wrote:
>
> On Tuesday, July 7, 2020 1:09am, "Sean Christopherson" <sean.j.christopherson@intel.com> said:
> Sean, are you the one who would get this particular fix pushed into Linus's
> tree, by the way? The "maintainership" is not clear to me.
Nope, I'm just here to complain and nitpick :-) There's no direct maintainer
for virtext.h so it falls under the higher level arch/x86 umbrella, i.e. I
expect Boris/Thomas/Ingo will pick this up.
next prev parent reply other threads:[~2020-07-07 19:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 14:45 [PATCH v2] Fix undefined operation VMXOFF during reboot and crash David P. Reed
2020-06-25 14:59 ` David P. Reed
2020-06-29 20:54 ` David P. Reed
2020-06-29 21:22 ` Andy Lutomirski
2020-06-29 21:49 ` Sean Christopherson
2020-06-29 22:46 ` David P. Reed
2020-07-04 20:38 ` [PATCH v3 0/3] " David P. Reed
2020-07-04 20:38 ` [PATCH v3 1/3] Correct asm VMXOFF side effects David P. Reed
2020-07-05 5:46 ` Randy Dunlap
2020-07-04 20:38 ` [PATCH v3 2/3] Fix undefined operation fault that can hang a cpu on crash or panic David P. Reed
2020-07-05 18:22 ` Andy Lutomirski
2020-07-05 19:52 ` David P. Reed
2020-07-05 20:55 ` Andy Lutomirski
2020-07-05 22:07 ` David P. Reed
2020-07-07 5:09 ` Sean Christopherson
2020-07-07 19:09 ` David P. Reed
2020-07-07 19:24 ` Sean Christopherson [this message]
2020-07-07 19:52 ` David P. Reed
2020-07-04 20:38 ` [PATCH v3 3/3] Force all cpus to exit VMX root operation on crash/panic reliably David P. Reed
2020-07-05 18:26 ` Andy Lutomirski
2020-07-05 20:00 ` David P. Reed
2020-07-05 20:53 ` Andy Lutomirski
2020-07-07 5:29 ` Sean Christopherson
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=20200707192455.GI20096@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=alexandre.chartre@oracle.com \
--cc=allison@lohutok.net \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dpreed@deepplum.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=info@metux.net \
--cc=jannh@google.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=martin.molnar.programming@gmail.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--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).