All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@linux.intel.com>
To: torvalds@linux-foundation.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	Dave Hansen <dave.hansen@linux.intel.com>
Subject: [GIT PULL] x86/tdx for 7.3-rc1
Date: Tue, 18 Aug 2026 08:06:13 -0700	[thread overview]
Message-ID: <20260818150613.2809384-1-dave.hansen@linux.intel.com> (raw)

Hi Linus,

Please pull some x86/tdx changes for 7.3-rc1. TDX guests cause #VE
exceptions whenever they do port I/O. The guest then does some
instruction decoding and makes a call up to the host for help. That
decoding had a couple of bugs.

Fix those bugs. Use an existing and now shared KVM helper for one
of them.

--

The following changes since commit a13c140cc289c0b7b3770bce5b3ad42ab35074aa:

  Linux 7.2-rc3 (2026-07-12 14:16:39 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_tdx_for_7.3-rc1

for you to fetch changes up to 941370fc93cc3474e26811f4d3b062903eefe2cf:

  x86/tdx: Fix zero-extension for 32-bit port I/O (2026-07-13 14:45:07 -0700)

----------------------------------------------------------------
 * Fix TDX port I/O bugs

----------------------------------------------------------------
Kiryl Shutsemau (Meta) (3):
      x86/tdx: Fix off-by-one in port I/O handling
      x86/insn-eval: Move assign_register() out of KVM as insn_assign_reg()
      x86/tdx: Fix zero-extension for 32-bit port I/O

 arch/x86/coco/tdx/tdx.c          | 10 ++++------
 arch/x86/include/asm/insn-eval.h | 36 ++++++++++++++++++++++++++++++++++++
 arch/x86/kvm/emulate.c           | 26 ++++----------------------
 3 files changed, 44 insertions(+), 28 deletions(-)

             reply	other threads:[~2026-08-18 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18 15:06 Dave Hansen [this message]
2026-08-19  1:10 ` [GIT PULL] x86/tdx for 7.3-rc1 pr-tracker-bot
2026-08-19  1:10 ` pr-tracker-bot

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=20260818150613.2809384-1-dave.hansen@linux.intel.com \
    --to=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.