From: Kiryl Shutsemau <kas@kernel.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Kai Huang <kai.huang@intel.com>,
Sean Christopherson <seanjc@google.com>,
Borys Tsyrulnikov <tsyrulnikov.borys@gmail.com>,
linux-kernel@vger.kernel.org, linux-coco@lists.linux.dev,
kvm@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3 2/2] x86/tdx: Fix zero-extension for 32-bit port I/O
Date: Thu, 28 May 2026 11:14:38 +0100 [thread overview]
Message-ID: <ahgUBLjBRGhxULu3@thinkstation> (raw)
In-Reply-To: <5ed6121c-314e-4cf0-9a11-b0661c87c694@intel.com>
On Wed, May 27, 2026 at 10:45:28AM -0700, Dave Hansen wrote:
> On 5/27/26 05:05, Kiryl Shutsemau (Meta) wrote:
> ...
> > - /* Update part of the register affected by the emulated instruction */
> > - regs->ax &= ~mask;
> > + /*
> > + * IN writes the result into a sub-register of RAX. Only the
> > + * 32-bit form zero-extends; the smaller forms leave the upper
> > + * bits untouched:
> > + *
> > + * insn dest size bits written bits preserved
> > + * inb AL 1 RAX[ 7: 0] RAX[63: 8]
> > + * inw AX 2 RAX[15: 0] RAX[63:16]
> > + * inl EAX 4 RAX[63: 0] (none, zero-extended)
> > + *
> > + * 'mask' only covers the low 'size' bytes, which is exactly the
> > + * range affected for size 1 and 2. For size 4 the write also
> > + * clears RAX[63:32], so widen the clear-mask.
> > + */
> > + if (size == 4)
> > + regs->ax = 0;
> > + else
> > + regs->ax &= ~mask;
> > +
>
> Is there any way we could do this with fewer comments and more code?
>
> I mean, there's only three cases. Why have;
>
> u64 mask = GENMASK(BITS_PER_BYTE * size - 1, 0);
>
> When there are only 3 possible cases:
>
> 1 => 0xf
> 2 => 0xff
> 4 => 0xffff
>
> and one of those cases needs a special case on top of it.
>
> Maybe something like this?
>
> /* Clear out part of RAX so part of args.r11 can be OR'd in: */
> switch (size) {
> case 1:
> /* inb consumes lower 8 bits of r11: */
> regs->ax &= ~GENMASK_ULL(7, 0);
> args.r11 &= GENMASK_ULL(7, 0);
> break;
> case 2:
> /* inw consumes lower 16 bits of r11: */
> regs->ax &= ~GENMASK_ULL(15, 0);
> args.r11 &= GENMASK_ULL(15, 0);
> break;
> case 4:
> /* inl is weird and zeros the whole register: */
> regs->ax &= ~GENMASK_ULL(63, 0);
> /* But only consumes 32-bits from r11: */
> args.r11 &= GENMASK_ULL(31, 0);
> break;
> default:
> /* Probable TDX module bug. Illegal in[bwl] size: */
> WARN_ON_ONCE(1);
> success = 0;
> }
>
> if (success)
> regs->ax |= args.r11;
>
> It might need a temporary variable for args.r11, but you get the point.
> That's basically the data from the comment but written as code.
I hate how verbose it is. All these GENMASK_ULL() make it hard to
follow.
What about the patch below. Inspired by kvm's assign_register().
diff --git a/arch/x86/coco/tdx/tdx.c b/arch/x86/coco/tdx/tdx.c
index 65119362f9a2..460b9fbabf14 100644
--- a/arch/x86/coco/tdx/tdx.c
+++ b/arch/x86/coco/tdx/tdx.c
@@ -693,8 +693,8 @@ static bool handle_in(struct pt_regs *regs, int size, int port)
.r13 = PORT_READ,
.r14 = port,
};
- u64 mask = GENMASK(BITS_PER_BYTE * size - 1, 0);
bool success;
+ u32 val;
/*
* Emulate the I/O read via hypercall. More info about ABI can be found
@@ -703,10 +703,33 @@ static bool handle_in(struct pt_regs *regs, int size, int port)
*/
success = !__tdx_hypercall(&args);
- /* Update part of the register affected by the emulated instruction */
- regs->ax &= ~mask;
if (success)
- regs->ax |= args.r11 & mask;
+ val = args.r11;
+ else
+ val = 0;
+
+ /*
+ * IN writes the result into a sub-register of RAX.
+ *
+ * Only the 32-bit form zero-extends; the smaller forms leave
+ * the upper bits untouched.
+ */
+ switch (size) {
+ case 1:
+ *(u8 *)®s->ax = (u8)val;
+ break;
+ case 2:
+ *(u16 *)®s->ax = (u16)val;
+ break;
+ case 4:
+ /* zero-extended */
+ regs->ax = val;
+ break;
+ default:
+ /* Probable TDX module bug. Illegal in[bwl] size. */
+ WARN_ON_ONCE(1);
+ break;
+ }
return success;
}
--
Kiryl Shutsemau / Kirill A. Shutemov
next prev parent reply other threads:[~2026-05-28 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 12:05 [PATCH v3 0/2] x86/tdx: Port I/O emulation fixes Kiryl Shutsemau (Meta)
2026-05-27 12:05 ` [PATCH v3 1/2] x86/tdx: Fix off-by-one in port I/O handling Kiryl Shutsemau (Meta)
2026-05-27 15:38 ` Edgecombe, Rick P
2026-05-27 12:05 ` [PATCH v3 2/2] x86/tdx: Fix zero-extension for 32-bit port I/O Kiryl Shutsemau (Meta)
2026-05-27 15:45 ` Edgecombe, Rick P
2026-05-27 17:45 ` Dave Hansen
2026-05-28 10:14 ` Kiryl Shutsemau [this message]
2026-05-28 16:43 ` Dave Hansen
2026-05-28 17:25 ` Dave Hansen
2026-05-28 19:58 ` David Laight
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=ahgUBLjBRGhxULu3@thinkstation \
--to=kas@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=tsyrulnikov.borys@gmail.com \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox