From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 0A4C3E77188 for ; Fri, 3 Jan 2025 14:26:31 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.864580.1275786 (Exim 4.92) (envelope-from ) id 1tTicX-000740-RI; Fri, 03 Jan 2025 14:25:49 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 864580.1275786; Fri, 03 Jan 2025 14:25:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tTicX-00073t-OQ; Fri, 03 Jan 2025 14:25:49 +0000 Received: by outflank-mailman (input) for mailman id 864580; Fri, 03 Jan 2025 14:25:49 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1tTicX-00073n-1m for xen-devel@lists.xenproject.org; Fri, 03 Jan 2025 14:25:49 +0000 Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id 9f6e58ca-c9de-11ef-a0de-8be0dac302b0; Fri, 03 Jan 2025 15:25:47 +0100 (CET) Received: from zcs2-store8.inria.fr ([128.93.142.6]) by mail2-relais-roc.national.inria.fr with ESMTP; 03 Jan 2025 15:25:46 +0100 X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: 9f6e58ca-c9de-11ef-a0de-8be0dac302b0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=date:from:to:cc:message-id:subject:mime-version; bh=kt4M98Cy6jOnI51rllLEbPqEFW6bHVmTXKIBCBhaFSw=; b=dt8YoZtU3gEqPq4u7t1lMfBmf3bj7K6PdnjKzE3ZSQw/IZrKmNWQcOx2 oeEYwDOBs0k3ljGs0f7R1yP0l6coLO90T3IypSL1s4/hlKKdz/8eSZtRM Wfr8kPLQXOxhZfiInjHw7crjuoK8cTVwbBhIQR/6TMrRyhgCSzxBMfjMP E=; Authentication-Results: mail2-relais-roc.national.inria.fr; dkim=none (message not signed) header.i=none; spf=Pass smtp.mailfrom=fonyuy-asheri.caleb@inria.fr; spf=None smtp.helo=postmaster@zcs2-store8.inria.fr Received-SPF: Pass (mail2-relais-roc.national.inria.fr: domain of fonyuy-asheri.caleb@inria.fr designates 128.93.142.6 as permitted sender) identity=mailfrom; client-ip=128.93.142.6; receiver=mail2-relais-roc.national.inria.fr; envelope-from="fonyuy-asheri.caleb@inria.fr"; x-sender="fonyuy-asheri.caleb@inria.fr"; x-conformance=spf_only; x-record-type="v=spf1"; x-record-text="v=spf1 include:mailout.safebrands.com a:basic-mail.safebrands.com a:basic-mail01.safebrands.com a:basic-mail02.safebrands.com ip4:128.93.142.0/24 ip4:192.134.164.0/24 ip4:128.93.162.160 ip4:128.93.162.3 ip4:128.93.162.88 ip4:89.107.174.7 mx ~all" Received-SPF: None (mail2-relais-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@zcs2-store8.inria.fr) identity=helo; client-ip=128.93.142.6; receiver=mail2-relais-roc.national.inria.fr; envelope-from="fonyuy-asheri.caleb@inria.fr"; x-sender="postmaster@zcs2-store8.inria.fr"; x-conformance=spf_only X-IronPort-AV: E=Sophos;i="6.12,286,1728943200"; d="scan'208,217";a="201340769" X-MGA-submission: =?us-ascii?q?MDEckorXfVwRa+NVnxExk2KhM5sE//nkGUPG9B?= =?us-ascii?q?nV9gtLTczUfcAZUWsDdOmJ3+p1YUVaC+RhsJJKLgByboxMq0a/SR0cHE?= =?us-ascii?q?PHwLE8hOSRU5u9+wUVsWWYsniPk9O3YlaPK6oc4c2/zus2HIxTFe+GpI?= =?us-ascii?q?1LXP8XwhJZPml8Be34gw89uQ=3D=3D?= Date: Fri, 3 Jan 2025 15:25:46 +0100 (CET) From: Fonyuy-Asheri Caleb To: xen-devel Cc: Jan Beulich , Andrew Cooper Message-ID: <944938302.6053932.1735914346495.JavaMail.zimbra@inria.fr> Subject: Help With Identifying CPUID faulting logic in Xen code MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_87ed86ca-dcae-4c7f-b4d9-51ed8a12c060" X-Originating-IP: [176.180.88.57] X-Mailer: Zimbra 10.1.3_GA_4699 (ZimbraWebClient - GC131 (Linux)/10.1.3_GA_4703) Thread-Index: /woCOpHH4VcfB1CDYgx0B/Ta9wD+cA== Thread-Topic: Help With Identifying CPUID faulting logic in Xen code --=_87ed86ca-dcae-4c7f-b4d9-51ed8a12c060 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 --=_87ed86ca-dcae-4c7f-b4d9-51ed8a12c060 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

I am interested in finding understanding how xen handles= CPUID faulting and 
VM exits in general. Please c= an 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 t= he features defined in cpuid-autogen.h file 
depen= ding on the guest type. 

= I started looking at the file xen/arch/x86/cpuid.c but don't really know wh= ich other 
files to check next. 

Thanks

Caleb
--=_87ed86ca-dcae-4c7f-b4d9-51ed8a12c060--