From: Borislav Petkov <bp@suse.de>
To: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>
Cc: "Singh, Brijesh" <brijesh.singh@amd.com>,
Kairui Song <kasong@redhat.com>, Baoquan He <bhe@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"dyoung@redhat.com" <dyoung@redhat.com>
Subject: Re: [PATCH] x86/boot: Fix kexec booting failure after SEV early boot support
Date: Wed, 26 Sep 2018 15:18:56 +0200 [thread overview]
Message-ID: <20180926131856.GD6920@zn.tnic> (raw)
In-Reply-To: <3b41fee3-e2f6-2e36-d2ca-1074c5f62bb8@amd.com>
On Wed, Sep 26, 2018 at 01:01:00PM +0000, Lendacky, Thomas wrote:
> No concern from me. The original version of the patch did not cache the
> value, that was added based on the patch series feedback. So, if there
> is no concern about executing some extra CPUID/RDMSR instructions, then
> it would certainly simplify the code quite a bit.
Yeah, I think it was me who suggested to cache it but having simpler
code greatly outweighs the minute caching win.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@suse.de>
To: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>
Cc: Baoquan He <bhe@redhat.com>, Kairui Song <kasong@redhat.com>,
"Singh, Brijesh" <brijesh.singh@amd.com>,
"x86@kernel.org" <x86@kernel.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"dyoung@redhat.com" <dyoung@redhat.com>
Subject: Re: [PATCH] x86/boot: Fix kexec booting failure after SEV early boot support
Date: Wed, 26 Sep 2018 15:18:56 +0200 [thread overview]
Message-ID: <20180926131856.GD6920@zn.tnic> (raw)
In-Reply-To: <3b41fee3-e2f6-2e36-d2ca-1074c5f62bb8@amd.com>
On Wed, Sep 26, 2018 at 01:01:00PM +0000, Lendacky, Thomas wrote:
> No concern from me. The original version of the patch did not cache the
> value, that was added based on the patch series feedback. So, if there
> is no concern about executing some extra CPUID/RDMSR instructions, then
> it would certainly simplify the code quite a bit.
Yeah, I think it was me who suggested to cache it but having simpler
code greatly outweighs the minute caching win.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2018-09-26 13:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 11:10 [PATCH] x86/boot: Fix kexec booting failure after SEV early boot support Kairui Song
2018-09-25 11:10 ` Kairui Song
2018-09-25 14:33 ` Lendacky, Thomas
2018-09-25 14:33 ` Lendacky, Thomas
2018-09-25 17:26 ` Borislav Petkov
2018-09-25 17:26 ` Borislav Petkov
2018-09-26 7:32 ` Baoquan He
2018-09-26 7:32 ` Baoquan He
2018-09-26 10:52 ` Kairui Song
2018-09-26 10:52 ` Kairui Song
2018-09-26 11:22 ` Baoquan He
2018-09-26 11:22 ` Baoquan He
2018-09-26 13:01 ` Lendacky, Thomas
2018-09-26 13:01 ` Lendacky, Thomas
2018-09-26 13:18 ` Borislav Petkov [this message]
2018-09-26 13:18 ` Borislav Petkov
2018-09-26 13:21 ` Baoquan He
2018-09-26 13:21 ` Baoquan He
-- strict thread matches above, loose matches on Subject: below --
2018-09-27 12:38 Kairui Song
2018-09-27 12:38 ` Kairui Song
2018-09-27 13:16 ` Lendacky, Thomas
2018-09-27 13:16 ` Lendacky, Thomas
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=20180926131856.GD6920@zn.tnic \
--to=bp@suse.de \
--cc=Thomas.Lendacky@amd.com \
--cc=bhe@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=kasong@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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 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.