From: Fonyuy-Asheri Caleb <fonyuy-asheri.caleb@inria.fr>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Help With Identifying CPUID faulting logic in Xen code
Date: Fri, 3 Jan 2025 15:25:46 +0100 (CET) [thread overview]
Message-ID: <944938302.6053932.1735914346495.JavaMail.zimbra@inria.fr> (raw)
[-- 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 --]
next reply other threads:[~2025-01-03 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 14:25 Fonyuy-Asheri Caleb [this message]
2025-01-03 14:35 ` Help With Identifying CPUID faulting logic in Xen code Andrew Cooper
2025-01-03 14:54 ` Fonyuy-Asheri Caleb
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=944938302.6053932.1735914346495.JavaMail.zimbra@inria.fr \
--to=fonyuy-asheri.caleb@inria.fr \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.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 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.