From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Uros Bizjak <ubizjak@gmail.com>,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>, Andy Lutomirski <luto@kernel.org>,
Brian Gerst <brgerst@gmail.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
x86@kernel.org
Subject: Re: [tip: x86/fpu] x86/fpu: Use XSAVE{,OPT,C,S} and XRSTOR{,S} mnemonics in xstate.h
Date: Mon, 17 Mar 2025 11:49:54 -0700 [thread overview]
Message-ID: <05953E05-28D0-4640-9ECF-BDDB9521ECD3@zytor.com> (raw)
In-Reply-To: <20250317184839.GIZ9huh0WS7cOFXz0X@fat_crate.local>
On March 17, 2025 11:48:39 AM PDT, Borislav Petkov <bp@alien8.de> wrote:
>On Mon, Mar 17, 2025 at 11:38:12AM -0700, H. Peter Anvin wrote:
>> Ok, I'm going to argue, but only because the argument is called "st" and the
>> assembly parameter "xa". That's needlessly different and means having to
>> look extra hard
>>
>> We can obviously not use the same token, but IMO it would make a lot more
>> sense to call one of them _st or perhaps st_p (being a pointer).
>
>Already documented:
>
>https://git.kernel.org/tip/4348e9177813656d5d8bd18f34b3e611df004032
>
>Got tired of discussing the obvious.
>
Ok.
prev parent reply other threads:[~2025-03-17 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 13:02 [PATCH] " Uros Bizjak
2025-03-13 17:50 ` [tip: x86/fpu] " tip-bot2 for Uros Bizjak
2025-03-17 10:14 ` Borislav Petkov
2025-03-17 10:28 ` Uros Bizjak
2025-03-17 10:46 ` Borislav Petkov
2025-03-17 11:06 ` Uros Bizjak
2025-03-17 18:38 ` H. Peter Anvin
2025-03-17 18:48 ` Borislav Petkov
2025-03-17 18:49 ` H. Peter Anvin [this message]
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=05953E05-28D0-4640-9ECF-BDDB9521ECD3@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®