From: "H. Peter Anvin" <hpa@zytor.com>
To: Khalid Ali <khaliidcaliy@gmail.com>,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, ubizjak@gmail.com
Cc: x86@kernel.org, linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] Recieve boot_param from RDI Instead of RSI
Date: Mon, 23 Jun 2025 08:24:16 -0700 [thread overview]
Message-ID: <2D63735B-FA76-428E-8F68-8EBCAEA0985E@zytor.com> (raw)
In-Reply-To: <20250623081550.1262-1-khaliidcaliy@gmail.com>
On June 23, 2025 1:15:23 AM PDT, Khalid Ali <khaliidcaliy@gmail.com> wrote:
>From: Khalid Ali <khaliidcaliy@gmail.com>
>
>Adjust the kernel entry point to recieve arguments from RDI instead of
>RSI.
>
>Signed-off-by: Khalid Ali <khaliidcaliy@gmail.com>
>---
> arch/x86/kernel/head_64.S | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/arch/x86/kernel/head_64.S b/arch/x86/kernel/head_64.S
>index dfb5390e5c9a..d24fea15b6a6 100644
>--- a/arch/x86/kernel/head_64.S
>+++ b/arch/x86/kernel/head_64.S
>@@ -43,7 +43,7 @@ SYM_CODE_START_NOALIGN(startup_64)
> * for us. These identity mapped page tables map all of the
> * kernel pages and possibly all of memory.
> *
>- * %RSI holds the physical address of the boot_params structure
>+ * %RDI holds the physical address of the boot_params structure
> * provided by the bootloader. Preserve it in %R15 so C function calls
> * will not clobber it.
> *
>@@ -56,7 +56,7 @@ SYM_CODE_START_NOALIGN(startup_64)
> * compiled to run at we first fixup the physical addresses in our page
> * tables and then reload them.
> */
>- mov %rsi, %r15
>+ mov %rdi, %r15
>
> /* Set up the stack for verify_cpu() */
> leaq __top_init_kernel_stack(%rip), %rsp
This is an ABI.
Nacked-by: H. Peter Anvin <hpa@zytor.com>
next prev parent reply other threads:[~2025-06-23 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 8:15 Khalid Ali
2025-06-23 15:24 ` H. Peter Anvin [this message]
2025-06-23 16:16 ` Khalid Ali
2025-06-23 17:58 ` [PATCH " Brian Gerst
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=2D63735B-FA76-428E-8F68-8EBCAEA0985E@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--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®