From: Sean Christopherson <seanjc@google.com>
To: Vasant Karasulli <vkarasulli@suse.de>
Cc: kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v1] x86: efi: set up the IDT before accessing MSRs.
Date: Fri, 21 Oct 2022 20:45:22 +0000 [thread overview]
Message-ID: <Y1ME4jXPwsgT67B8@google.com> (raw)
In-Reply-To: <Y0gVW+wzPSEPeci7@vasant-suse>
On Thu, Oct 13, 2022, Vasant Karasulli wrote:
> Hi Sean,
>
> > 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.
>
> Yes, I think my client was stripping trailing whitespaces. Do you want me
> to send a new version of the patch with that formatting?
No need, I'll put together a KUT PULL request next unless Paolo beats me to the
punch.
prev parent reply other threads:[~2022-10-21 20:46 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
2022-10-13 13:40 ` Vasant Karasulli
2022-10-21 20:45 ` Sean Christopherson [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=Y1ME4jXPwsgT67B8@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=vkarasulli@suse.de \
/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