public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ryan Afranji" <afranji@google.com>
To: devel@edk2.groups.io
Cc: jun.nakajima@intel.com, min.m.xu@intel.com, jiewen.yao@intel.com,
	 erdemaktas@google.com, vannapurve@google.com,
	 Ryan Afranji <afranji@google.com>
Subject: [V1 PATCH 1/1] OvmfPkg: Add INVD case in #VE handler
Date: Thu,  8 Dec 2022 00:51:15 +0000	[thread overview]
Message-ID: <20221208005115.3880077-1-afranji@google.com> (raw)

According to the Intel GHCI specification document section 2.4.1, the
goal for instructions that do not have a corresponding TDCALL is for the
handler to treat the instruction as a NOP.

INVD does not have a corresponding TDCALL. This patch makes the #VE
handler treat INVD as a NOP.

Signed-off-by: Ryan Afranji <afranji@google.com>
---
 OvmfPkg/Library/CcExitLib/CcExitVeHandler.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/OvmfPkg/Library/CcExitLib/CcExitVeHandler.c b/OvmfPkg/Library/CcExitLib/CcExitVeHandler.c
index c35f65a649..3798c2bb13 100644
--- a/OvmfPkg/Library/CcExitLib/CcExitVeHandler.c
+++ b/OvmfPkg/Library/CcExitLib/CcExitVeHandler.c
@@ -541,6 +541,7 @@ CcExitHandleVe (
     case EXIT_REASON_MONITOR_INSTRUCTION:
     case EXIT_REASON_WBINVD:
     case EXIT_REASON_RDPMC:
+    case EXIT_REASON_INVD:
       /* Handle as nops. */
       break;
 
-- 
2.39.0.rc1.256.g54fd8350bd-goog


             reply	other threads:[~2022-12-08  0:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08  0:51 Ryan Afranji [this message]
2022-12-09  6:49 ` [V1 PATCH 1/1] OvmfPkg: Add INVD case in #VE handler Yao, Jiewen
     [not found] ` <172F0D44D4F3B834.22457@groups.io>
2022-12-09  7:11   ` [edk2-devel] " Yao, Jiewen

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-list 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=20221208005115.3880077-1-afranji@google.com \
    --to=devel@edk2.groups.io \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox