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 6.4
Date: Thu, 27 Apr 2023 11:15:48 -0700 [thread overview]
Message-ID: <20230427181548.1070481-1-dave.hansen@linux.intel.com> (raw)
Hi Linus,
Please pull a single x86/tdx change for 6.4.
The original assembly here took two flags in %RSI to tweak its behavior
at runtime. PeterZ recently axed one flag. Kill the other and tweak
the 'output' mode with an assembly macro instead. This results in
elimination of one push/pop pair and overall easier to read assembly.
--
The following changes since commit e8d018dd0257f744ca50a729e3d042cf2ec9da65:
Linux 6.3-rc3 (2023-03-19 13:27:55 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/daveh/devel.git tags/test.1682619270.x86_tdx_for_6.4
for you to fetch changes up to 7a3a401874bea02f568aa416ac29170d8cde0dc2:
x86/tdx: Drop flags from __tdx_hypercall() (2023-03-22 11:36:05 -0700)
----------------------------------------------------------------
* Do conditional __tdx_hypercall() 'output' processing via an
assembly macro argument rather than a runtime register.
----------------------------------------------------------------
Kirill A. Shutemov (1):
x86/tdx: Drop flags from __tdx_hypercall()
arch/x86/boot/compressed/tdx.c | 4 +--
arch/x86/coco/tdx/tdcall.S | 66 ++++++++++++++++++++++-----------------
arch/x86/coco/tdx/tdx.c | 18 +++++------
arch/x86/include/asm/shared/tdx.h | 5 ++-
4 files changed, 51 insertions(+), 42 deletions(-)
next reply other threads:[~2023-04-27 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 18:15 Dave Hansen [this message]
2023-04-27 18:30 ` [GIT PULL] x86/tdx for 6.4 Dave Hansen
2023-04-28 17:23 ` 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=20230427181548.1070481-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox