All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Vasant Karasulli <vkarasulli@suse.de>
Cc: kvm@vger.kernel.org, Thomas.Lendacky@amd.com, bp@alien8.de,
	erdemaktas@google.com, jroedel@suse.de, marcorr@google.com,
	pbonzini@redhat.com, rientjes@google.com, varad.gautam@suse.com,
	zxwang42@gmail.com
Subject: Re: [kvm-unit-tests PATCH v1] x86: efi: set up the IDT before accessing MSRs.
Date: Thu, 25 Aug 2022 21:51:03 +0000	[thread overview]
Message-ID: <YwfuxxgGFVDpLOOR@google.com> (raw)
In-Reply-To: <20220823094328.8458-1-vkarasulli@suse.de>

On Tue, Aug 23, 2022, Vasant Karasulli wrote:
> Reading or writing MSR_IA32_APICBASE is typically an intercepted
> operation and causes #VC exception when the test is launched as
> an SEV-ES guest.
> 
> So calling pre_boot_apic_id() and reset_apic() before the IDT is
> set up in setup_idt() and load_idt() might cause problems.
> 
> Hence move percpu data setup and reset_apic() call after
> setup_idt() and load_idt().
> 
> Fixes: 3c50214c97f173f5e0f82c7f248a7c62707d8748 (x86: efi: Provide percpu storage)
> Signed-off-by: Vasant Karasulli <vkarasulli@suse.de>
> ---

Reviewed-by: Sean Christopherson <seanjc@google.com>

>  lib/x86/setup.c | 20 ++++++++++++--------
>  1 file changed, 12 insertions(+), 8 deletions(-)
> 
> diff --git a/lib/x86/setup.c b/lib/x86/setup.c
> index 7df0256..712e292 100644
> --- a/lib/x86/setup.c
> +++ b/lib/x86/setup.c
> @@ -192,8 +192,6 @@ static void setup_segments64(void)
>  	write_gs(KERNEL_DS);
>  	write_ss(KERNEL_DS);
> 
> -	/* Setup percpu base */
> -	wrmsr(MSR_GS_BASE, (u64)&__percpu_data[pre_boot_apic_id()]);
> 
>  	/*
>  	 * Update the code segment by putting it on the stack before the return
> @@ -322,7 +320,7 @@ efi_status_t setup_efi(efi_bootinfo_t *efi_bootinfo)
>  		}
>  		return status;
>  	}
> -
> +

Huh.  This causes a conflict for me.  My local repo has a tab here that is
presumably being removed, but this patch doesn't have anything.  If I manually
add back the tab, all is well.  I suspect your client may be stripping trailing
whitespace.

  reply	other threads:[~2022-08-25 21:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23  9:43 [kvm-unit-tests PATCH v1] x86: efi: set up the IDT before accessing MSRs Vasant Karasulli
2022-08-25 21:51 ` Sean Christopherson [this message]
2022-10-13 13:40   ` Vasant Karasulli
2022-10-21 20:45     ` Sean Christopherson

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=YwfuxxgGFVDpLOOR@google.com \
    --to=seanjc@google.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=bp@alien8.de \
    --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=vkarasulli@suse.de \
    --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.