From: Sean Christopherson <seanjc@google.com>
To: Varad Gautam <varad.gautam@suse.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, drjones@redhat.com,
marcorr@google.com, zxwang42@gmail.com, erdemaktas@google.com,
rientjes@google.com, brijesh.singh@amd.com,
Thomas.Lendacky@amd.com, jroedel@suse.de, bp@suse.de
Subject: Re: [kvm-unit-tests PATCH v2 05/10] x86: efi: Stop using UEFI-provided stack
Date: Wed, 13 Apr 2022 16:20:14 +0000 [thread overview]
Message-ID: <Ylb4PnJ2WQa2UO0w@google.com> (raw)
In-Reply-To: <20220412173407.13637-6-varad.gautam@suse.com>
On Tue, Apr 12, 2022, Varad Gautam wrote:
> UEFI test builds currently use the stack pointer configured by the
> UEFI implementation.
>
> Reserve stack space in .data for EFI testcases and switch %rsp to
> use this memory on early boot. This provides one 4K page per CPU
> to store its stack / percpu data.
>
> Signed-off-by: Varad Gautam <varad.gautam@suse.com>
> ---
> x86/efi/crt0-efi-x86_64.S | 3 +++
> x86/efi/efistart64.S | 8 ++++++++
> 2 files changed, 11 insertions(+)
>
> diff --git a/x86/efi/crt0-efi-x86_64.S b/x86/efi/crt0-efi-x86_64.S
> index eaf1656..1708ed5 100644
> --- a/x86/efi/crt0-efi-x86_64.S
> +++ b/x86/efi/crt0-efi-x86_64.S
> @@ -58,6 +58,9 @@ _start:
> popq %rdi
> popq %rsi
>
> + /* Switch away from EFI stack. */
> + lea stacktop(%rip), %rsp
> +
> call efi_main
> addq $8, %rsp
>
> diff --git a/x86/efi/efistart64.S b/x86/efi/efistart64.S
> index 8eadca5..cb08230 100644
> --- a/x86/efi/efistart64.S
> +++ b/x86/efi/efistart64.S
> @@ -6,6 +6,14 @@
>
> .data
>
> +max_cpus = MAX_TEST_CPUS
Why declare max_cpus? MAX_TEST_CPUS can be used directly.
> +
Rather than align the stack top, wouldn't it be easier and more obvious to the
reader to pre-align to?
.align PAGE_SIZE
> +/* Reserve stack in .data */
> + . = . + 4096 * max_cpus
Use PAGE_SIZE instead of open coding 4096.
E.g. this works for me with my MSR_GS_BASE suggestion in the next patch (spoiler
alert).
/* Reserve stack in .data */
.data
.align PAGE_SIZE
. = . + PAGE_SIZE * MAX_TEST_CPUS
.globl stacktop
stacktop:
> + .align 16
> +.globl stacktop
> +stacktop:
> +
> .align PAGE_SIZE
> .globl ptl2
> ptl2:
> --
> 2.32.0
>
next prev parent reply other threads:[~2022-04-13 16:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 17:33 [kvm-unit-tests PATCH v2 00/10] SMP Support for x86 UEFI Tests Varad Gautam
2022-04-12 17:33 ` [kvm-unit-tests PATCH v2 01/10] x86: Move ap_init() to smp.c Varad Gautam
2022-04-13 15:16 ` Sean Christopherson
2022-04-13 18:44 ` Sean Christopherson
2022-04-13 18:55 ` Sean Christopherson
2022-04-13 18:59 ` Sean Christopherson
2022-04-13 19:01 ` Sean Christopherson
2022-04-13 19:04 ` Sean Christopherson
2022-04-12 17:33 ` [kvm-unit-tests PATCH v2 02/10] x86: Move load_idt() to desc.c Varad Gautam
2022-04-13 15:19 ` Sean Christopherson
2022-04-12 17:34 ` [kvm-unit-tests PATCH v2 03/10] x86: desc: Split IDT entry setup into a generic helper Varad Gautam
2022-04-13 16:35 ` Sean Christopherson
2022-04-12 17:34 ` [kvm-unit-tests PATCH v2 04/10] x86: Move load_gdt_tss() to desc.c Varad Gautam
2022-04-13 15:58 ` Sean Christopherson
2022-04-12 17:34 ` [kvm-unit-tests PATCH v2 05/10] x86: efi: Stop using UEFI-provided stack Varad Gautam
2022-04-13 16:20 ` Sean Christopherson [this message]
2022-04-12 17:34 ` [kvm-unit-tests PATCH v2 06/10] x86: efi: Stop using UEFI-provided %gs for percpu storage Varad Gautam
2022-04-13 16:23 ` Sean Christopherson
2022-04-12 17:34 ` [kvm-unit-tests PATCH v2 07/10] x86: efi, smp: Transition APs from 16-bit to 32-bit mode Varad Gautam
2022-04-13 19:17 ` Sean Christopherson
2022-04-12 17:34 ` [kvm-unit-tests PATCH v2 08/10] x86: Move 32-bit bringup routines to start32.S Varad Gautam
2022-04-13 19:33 ` Sean Christopherson
2022-04-12 17:34 ` [kvm-unit-tests PATCH v2 09/10] x86: efi, smp: Transition APs from 32-bit to 64-bit mode Varad Gautam
2022-04-12 17:34 ` [kvm-unit-tests PATCH v2 10/10] x86: Provide a common 64-bit AP entrypoint for EFI and non-EFI Varad Gautam
2022-04-13 19:55 ` Sean Christopherson
2022-04-13 19:57 ` [kvm-unit-tests PATCH v2 00/10] SMP Support for x86 UEFI Tests Sean Christopherson
2022-04-26 11:51 ` Varad Gautam
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=Ylb4PnJ2WQa2UO0w@google.com \
--to=seanjc@google.com \
--cc=Thomas.Lendacky@amd.com \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=drjones@redhat.com \
--cc=erdemaktas@google.com \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=marcorr@google.com \
--cc=pbonzini@redhat.com \
--cc=rientjes@google.com \
--cc=varad.gautam@suse.com \
--cc=zxwang42@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.