On March 16, 2022 4:37 PM, Ni Ray wrote:
>
> GetProcessorInfo() can return the information for index#0 CPU.
> Other suggestions look good to me.
>
Agree. It will be updated in the next version.
Thanks
Min
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
Vie
GetProcessorInfo() can return the information for index#0 CPU.
Other suggestions look good to me.
-Original Message-
From: Xu, Min M
Sent: Wednesday, March 16, 2022 4:32 PM
To: Ni, Ray ; devel@edk2.groups.io
Cc: Brijesh Singh ; Aktas, Erdem
; James Bottomley ; Yao, Jiewen
; Tom Lendack
On March 15, 2022 3:58 PM, Ni Ray wrote:
>
> Min,
> I don't quite understand.
>
> Of all MP services, the TDX version only supports:
> * GetNumberOfProcessors
> * GetProcessorInfo
>
> And even when TDX MP returns 3 or 4 threads from GetNumberOfProcessors(),
> StartupAllAPs() is an NOP.
> Will th
Min,
I don't quite understand.
Of all MP services, the TDX version only supports:
* GetNumberOfProcessors
* GetProcessorInfo
And even when TDX MP returns 3 or 4 threads from GetNumberOfProcessors(),
StartupAllAPs() is an NOP.
Will that cause any issue?
Can you avoid running MP driver when TDX i
RFC: https://bugzilla.tianocore.org/show_bug.cgi?id=3429
In TDVF BSP and APs are simplified. BSP is the vCPU-0, while the others
are treated as APs.
So MP intialization is rather simple. The processor info is retrieved by
TDCALL, ApWorker is not supported, BSP is always the working processor,
whi
