public inbox for linux-sgx@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Jarkko Sakkinen <jarkko@kernel.org>, Uros Bizjak <ubizjak@gmail.com>
Cc: linux-sgx@vger.kernel.org, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86/sgx: Use ENCLS mnemonic in <kernel/cpu/sgx/encls.h>
Date: Tue, 17 Jun 2025 08:01:28 -0700	[thread overview]
Message-ID: <26b8939e-796a-4581-a41c-42e3582326bd@intel.com> (raw)
In-Reply-To: <aFF_UwJ2XlFQSZOi@kernel.org>

On 6/17/25 07:44, Jarkko Sakkinen wrote:
> I don't really see how this is that useful. That said, f a bug fix or
> feature used encls mnemonic, I'd had no problems with acking it.

It's not _that_ useful.

But old assemblers that we still want to use *NEVER* have support for
newfanlged instructions, so we always add new instructions with ".byte".
Then, a few years down the road when we've moved to just old assemblers
instead of super old assemblers, we move to the real instruction names.

This is all business as usual.

  reply	other threads:[~2025-06-17 15:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  8:56 [PATCH] x86/sgx: Use ENCLS mnemonic in <kernel/cpu/sgx/encls.h> Uros Bizjak
2025-06-17 14:44 ` Jarkko Sakkinen
2025-06-17 15:01   ` Dave Hansen [this message]
2025-06-17 16:20     ` Uros Bizjak
2025-06-24 20:49       ` Jarkko Sakkinen
2025-06-24 20:47     ` Jarkko Sakkinen

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=26b8939e-796a-4581-a41c-42e3582326bd@intel.com \
    --to=dave.hansen@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jarkko@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sgx@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=ubizjak@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