* Help With Identifying CPUID faulting logic in Xen code
@ 2025-01-03 14:25 Fonyuy-Asheri Caleb
2025-01-03 14:35 ` Andrew Cooper
0 siblings, 1 reply; 3+ messages in thread
From: Fonyuy-Asheri Caleb @ 2025-01-03 14:25 UTC (permalink / raw)
To: xen-devel; +Cc: Jan Beulich, Andrew Cooper
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
Hello,
I am interested in finding understanding how xen handles CPUID faulting and
VM exits in general. Please can someone indicate to me the concerned files?
I want to know how xen detects the execution of the CPUID instruction and
ensures a guest only gets the features defined in cpuid-autogen.h file
depending on the guest type.
I started looking at the file xen/arch/x86/cpuid.c but don't really know which other
files to check next.
Thanks
Caleb
[-- Attachment #2: Type: text/html, Size: 15504 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Help With Identifying CPUID faulting logic in Xen code
2025-01-03 14:25 Help With Identifying CPUID faulting logic in Xen code Fonyuy-Asheri Caleb
@ 2025-01-03 14:35 ` Andrew Cooper
2025-01-03 14:54 ` Fonyuy-Asheri Caleb
0 siblings, 1 reply; 3+ messages in thread
From: Andrew Cooper @ 2025-01-03 14:35 UTC (permalink / raw)
To: Fonyuy-Asheri Caleb, xen-devel; +Cc: Jan Beulich
On 03/01/2025 2:25 pm, Fonyuy-Asheri Caleb wrote:
> Hello,
>
> I am interested in finding understanding how xen handles CPUID
> faulting and
> VM exits in general. Please can someone indicate to me the concerned
> files?
>
> I want to know how xen detects the execution of the CPUID instruction and
> ensures a guest only gets the features defined in cpuid-autogen.h file
> depending on the guest type.
>
> I started looking at the file xen/arch/x86/cpuid.c but don't really
> know which other
> files to check next.
https://xenbits.xen.org/docs/unstable/features/feature-levelling.html
has a reasonable introduction. Being nearly a decade old, it's slightly
stale. AMD now have CPUID Faulting capability too, new in Zen4 CPUs IIRC.
LCAP_faulting specifically is the constant you're looking for, in the
Xen code.
~Andrew
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Help With Identifying CPUID faulting logic in Xen code
2025-01-03 14:35 ` Andrew Cooper
@ 2025-01-03 14:54 ` Fonyuy-Asheri Caleb
0 siblings, 0 replies; 3+ messages in thread
From: Fonyuy-Asheri Caleb @ 2025-01-03 14:54 UTC (permalink / raw)
To: Andrew Cooper; +Cc: xen-devel, Jan Beulich
Thank you
Caleb
----- Original Message -----
> From: "Andrew Cooper" <andrew.cooper3@citrix.com>
> To: "Fonyuy-Asheri Caleb" <fonyuy-asheri.caleb@inria.fr>, "xen-devel" <xen-devel@lists.xenproject.org>
> Cc: "Jan Beulich" <jbeulich@suse.com>
> Sent: Friday, January 3, 2025 3:35:43 PM
> Subject: Re: Help With Identifying CPUID faulting logic in Xen code
> On 03/01/2025 2:25 pm, Fonyuy-Asheri Caleb wrote:
>> Hello,
>>
>> I am interested in finding understanding how xen handles CPUID
>> faulting and
>> VM exits in general. Please can someone indicate to me the concerned
>> files?
>>
>> I want to know how xen detects the execution of the CPUID instruction and
>> ensures a guest only gets the features defined in cpuid-autogen.h file
>> depending on the guest type.
>>
>> I started looking at the file xen/arch/x86/cpuid.c but don't really
>> know which other
>> files to check next.
>
> https://xenbits.xen.org/docs/unstable/features/feature-levelling.html
>
> has a reasonable introduction. Being nearly a decade old, it's slightly
> stale. AMD now have CPUID Faulting capability too, new in Zen4 CPUs IIRC.
>
> LCAP_faulting specifically is the constant you're looking for, in the
> Xen code.
>
> ~Andrew
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-01-03 14:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-01-03 14:25 Help With Identifying CPUID faulting logic in Xen code Fonyuy-Asheri Caleb
2025-01-03 14:35 ` Andrew Cooper
2025-01-03 14:54 ` Fonyuy-Asheri Caleb
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.