From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Min Xu <min.m.xu@intel.com>
Cc: devel@edk2.groups.io, Erdem Aktas <erdemaktas@google.com>,
James Bottomley <jejb@linux.ibm.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Ryan Afranji <afranji@google.com>
Subject: Re: [PATCH V3 0/2] [PATCH V1 0/2] Refactor TDX MmioExit
Date: Tue, 17 Jan 2023 12:33:12 +0100 [thread overview]
Message-ID: <20230117113312.2kw727uhdt323lal@sirius.home.kraxel.org> (raw)
In-Reply-To: <20230117074330.1058-1-min.m.xu@intel.com>
On Tue, Jan 17, 2023 at 03:43:28PM +0800, Min Xu wrote:
> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=4169
>
> The previous TDX MmioExit doesn't handle the Mmio instructions correctly
> in some scenarios. This patch-set refactors the implementation to fix the
> issues.
>
> Before the refactoring, common X86 instruction codes in CcExitVcHandler.c
> are moved to separate files (CcInstruction.h / CcInstruction.c) so that
> these codes can be re-used in TDX.
>
> Code: https://github.com/mxu9/edk2/tree/TdxMmioExit.v3
>
> v3 changes:
> - Handle the error if an error is returned from TdxMmioReadWrite.
> - Add more check in ParseMmioExitInstructions.
>
> v2 changes:
> - Add CpuDeadLoop () after each TDVMCALL(HALT) in VE handler. Because
> TDVMCALL(HALT) is not trusted.
> - Other minor changes such as deleting ASSERT in VE handler. Because
> any error in VE handler will trigger CpuDeadLoop (). So ASSERT is not
> needed any more.
Series:
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
next prev parent reply other threads:[~2023-01-17 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 7:43 [PATCH V3 0/2] [PATCH V1 0/2] Refactor TDX MmioExit Min Xu
2023-01-17 7:43 ` [PATCH V3 1/2] OvmfPkg/CcExitLib: Move common X86 instruction code to separate file Min Xu
2023-01-17 7:43 ` [PATCH V3 2/2] OvmfPkg/CcExitLib: Refactor TDX MmioExit Min Xu
2023-01-17 11:33 ` Gerd Hoffmann [this message]
2023-01-18 3:48 ` [edk2-devel] [PATCH V3 0/2] [PATCH V1 0/2] " 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=20230117113312.2kw727uhdt323lal@sirius.home.kraxel.org \
--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