[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Help understanding the x86 instruction decoder and emulator

To: xen-users@xxxxxxxxxxxxxxxxxxxx
From: Fonyuy-Asheri Caleb <fonyuy-asheri.caleb@xxxxxxxx>
Date: Wed, 6 Mar 2024 10:56:06 +0100 (CET)
Authentication-results: mail2-relais-roc.national.inria.fr; dkim=none (message not signed) header.i=none; spf=Pass smtp.mailfrom=fonyuy-asheri.caleb@xxxxxxxx; spf=None smtp.helo=postmaster@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 06 Mar 2024 09:56:54 +0000
List-id: Xen user discussion <xen-users.lists.xenproject.org>
Thread-index: +INHe+KUIjeSGX0j+hcGjndDmQDkUw==
Thread-topic: Help understanding the x86 instruction decoder and emulator

Hello,

I am new to xen code and have been trying to understand how xen handles emulated instructions like CPUID for PV VMs.

I looked into the files in xen/arch/x86/x86_emulate folder which handle emulation logic but I can't make out much sense from the logic.

Can someone please explain to me the logic behind this emulation and how it functions with the various cpu traps defined in xen/arch/x86/include/asm/processor.h

Thank you in advance for your help

Follow-Ups:
- Re: Help understanding the x86 instruction decoder and emulator
  - From: zithro

Prev by Date: [ANNOUNCE] Call for agenda items for Community Call
Next by Date: Re: Help understanding the x86 instruction decoder and emulator
Previous by thread: [ANNOUNCE] Call for agenda items for Community Call
Next by thread: Re: Help understanding the x86 instruction decoder and emulator
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.