From: "Huang, Kai" <kai.huang@intel.com>
To: "kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>
Cc: "arnd@kernel.org" <arnd@kernel.org>,
"Yao, Yuan" <yuan.yao@intel.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"bp@alien8.de" <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"Luck, Tony" <tony.luck@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>, "hpa@zytor.com" <hpa@zytor.com>,
"Yamahata, Isaku" <isaku.yamahata@intel.com>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>
Subject: Re: [PATCH] x86: tdx: hide unused tdx_dump_mce_info()
Date: Wed, 13 Dec 2023 20:41:36 +0000 [thread overview]
Message-ID: <0ee20c6422a9e1d53c2a1f9112d5dd8308eea1ba.camel@intel.com> (raw)
In-Reply-To: <de67b856-369c-41a2-8835-d25641eaeab6@intel.com>
On Wed, 2023-12-13 at 12:13 -0800, Dave Hansen wrote:
> On 12/13/23 12:11, Huang, Kai wrote:
> > > "The machine-check exception handler is expected to be implemented in the
> > > VMM."
> > I also agree. Thanks.
>
> Kai, could you please send a patch to fix this build problem that Arnd
> reported?
Turns out INTEL_TDX_GUEST selects X86_MCE, I think we can also just select
X86_MCE for TDX host?
config INTEL_TDX_GUEST
bool "Intel TDX (Trust Domain Extensions) - Guest Support"
depends on X86_64 && CPU_SUP_INTEL
...
select X86_MCE
next prev parent reply other threads:[~2023-12-13 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 21:36 [PATCH] x86: tdx: hide unused tdx_dump_mce_info() Arnd Bergmann
2023-12-12 21:42 ` Dave Hansen
2023-12-12 21:46 ` Borislav Petkov
2023-12-13 12:02 ` Kirill A. Shutemov
2023-12-13 20:11 ` Huang, Kai
2023-12-13 20:13 ` Dave Hansen
2023-12-13 20:29 ` Huang, Kai
2023-12-13 20:41 ` Huang, Kai [this message]
2023-12-13 22:32 ` Huang, Kai
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=0ee20c6422a9e1d53c2a1f9112d5dd8308eea1ba.camel@intel.com \
--to=kai.huang@intel.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=isaku.yamahata@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yuan.yao@intel.com \
/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).