[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9c7d99469179340eeecabaf3e9c414fc98900626.camel@intel.com>
Date: Mon, 27 Jun 2022 23:21:00 +1200
From: Kai Huang <kai.huang@...el.com>
To: "Yao, Jiewen" <jiewen.yao@...el.com>,
"Nakajima, Jun" <jun.nakajima@...el.com>,
Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@...ux.intel.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>,
"H . Peter Anvin" <hpa@...or.com>,
"Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>,
"Luck, Tony" <tony.luck@...el.com>,
Andi Kleen <ak@...ux.intel.com>,
Wander Lairson Costa <wander@...hat.com>,
Isaku Yamahata <isaku.yamahata@...il.com>,
"marcelo.cerri@...onical.com" <marcelo.cerri@...onical.com>,
"tim.gardner@...onical.com" <tim.gardner@...onical.com>,
"khalid.elmously@...onical.com" <khalid.elmously@...onical.com>,
"Cox, Philip" <philip.cox@...onical.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v8 2/5] x86/tdx: Add TDX Guest event notify interrupt
support
On Sat, 2022-06-25 at 15:35 +1200, Yao, Jiewen wrote:
> Thank you, Jun.
>
> Yes. I confirmed that we will include below change to GHCI.next spec.
>
> ================
> 3.5 TDG.VP.VMCALL<SetupEventNotifyInterrupt>
>
> From: "The host VMM should use SEAMCALL [TDWRVPS] leaf to inject an interrupt at the requested-interrupt vector into the TD via the posted-interrupt descriptor. "
>
> To: "The host VMM should use SEAMCALL [TDWRVPS] leaf to inject an interrupt at the requested-interrupt vector into the TD VCPU that executed TDG.VP.VMCALL <SetupEventNotifyInterrupt> via the posted-interrupt descriptor. "
>
Hi Sathy,
With this change, I don't think we should use system vector anymore. Instead,
we just need one non-migratable IRQ which has a fixed vector on a fixed cpu.
--
Thanks,
-Kai
Powered by blists - more mailing lists