From: "H. Peter Anvin" <hpa@zytor.com>
To: Brian Gerst <brgerst@gmail.com>, Khalid Ali <khaliidcaliy@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, ubizjak@gmail.com, x86@kernel.org,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/3] x86/boot: Supply boot_param in rdi instead of rsi from startup_64()
Date: Mon, 23 Jun 2025 17:43:27 -0700 [thread overview]
Message-ID: <9FE74F68-5CF9-4EFE-8271-551ECC9087B9@zytor.com> (raw)
In-Reply-To: <CAMzpN2jP_rtFjvL3NQLcwFCgY8uwbJvqbup-KFHVaaSh-oRCcQ@mail.gmail.com>
On June 23, 2025 12:24:50 PM PDT, Brian Gerst <brgerst@gmail.com> wrote:
>On Mon, Jun 23, 2025 at 2:40 PM Khalid Ali <khaliidcaliy@gmail.com> wrote:
>>
>> > This is also invoked by some external bootloaders that boot the ELF
>> > image directly, even though this is strongly discouraged.
>> >
>> > Therefore this patchset is NAKed with extreme prejudice.
>>
>> Thanks both of you peter and brian,
>>
>> however, the boot protocol document saying "%rsi must hold the base address of the struct boot_params",
>> it doesn't mention why. Maybe the document needs update to justify the reasons. I wouldn't have known it
>> if you didn't tell me, so this shouldn't confuse anyone else.
>
>The use of RSI was inherited from the 32-bit kernel, but the real
>reason is lost to history. It's just always been that way and there
>is no compelling reason to change it.
>
>
>Brian Gerst
>
The reason isn't lost to history: I picked %esi because I found that none of the weird bootloaders which looked the protected mode jump clobbered that particular register.
next prev parent reply other threads:[~2025-06-24 0:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 8:14 Khalid Ali
2025-06-23 12:33 ` Brian Gerst
2025-06-23 16:29 ` Khalid Ali
2025-06-23 18:19 ` H. Peter Anvin
2025-06-23 18:39 ` Khalid Ali
2025-06-23 19:24 ` Brian Gerst
2025-06-24 0:43 ` H. Peter Anvin [this message]
2025-06-24 0:49 ` H. Peter Anvin
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=9FE74F68-5CF9-4EFE-8271-551ECC9087B9@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=khaliidcaliy@gmail.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®