From: Ashok Raj <ashok_raj@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "X86 ML" <x86@kernel.org>, "Andrew Cooper" <amc96@srcf.net>,
LKML <linux-kernel@vger.kernel.org>,
"Ștefan Talpalaru" <stefantalpalaru@yahoo.com>,
"Ashok Raj" <ashok.raj@intel.com>
Subject: Re: [PATCH] x86/microcode/AMD: Attempt applying on every logical thread
Date: Sat, 5 Nov 2022 03:45:09 +0000 [thread overview]
Message-ID: <Y2XcRbaN9mDkWF9V@araj-dh-work> (raw)
In-Reply-To: <Yv4NXOlLHcx1Ghf3@araj-dh-work>
Hi Boris
On Thu, Aug 18, 2022 at 09:58:52AM +0000, Ashok Raj wrote:
> Hi Boris
>
> On Wed, Aug 17, 2022 at 11:56:02PM +0200, Borislav Petkov wrote:
> > On Wed, Aug 17, 2022 at 08:58:07PM +0000, Ashok Raj wrote:
> > > For this specific patch in question, its not for testing though.. Its
> > > required for functional purposes?
> >
> > From its commit message:
> >
> > "However, there are microcode patches which do per-thread modification,
> > see Link tag below.
> >
>
> I did read the commit log. I was just stating the fact that reload isn't
> just for testing, for e.g. in this case its required for functional
> reasons.
>
> if cpu_rev > ucode_rev, there is no need to reload microcode correct?
> There are a bunch of changes in the original post that seemed like it had
> nothing to do with force load on a sibling.
>
> Completely untested, no commit log to spare you from fixing them :-)
>
> Seemed like we were simply passing over each other with emails, thought
> I'll convey what I meant here via a patch. Hope this helps.
>
> lemme know what you think.
I saw your original patch got tipbot notification, but I don't see the
patch in the staging area.
I didn't see a followup to this, and wasn't sure if you fixed it some other
way.
I was cleaning up my mbox and want to be sure I didn't drop the ball.
Cheers,
Ashok
prev parent reply other threads:[~2022-11-05 3:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 12:00 [PATCH] x86/microcode/AMD: Attempt applying on every logical thread Borislav Petkov
2022-08-16 9:00 ` Ashok Raj
2022-08-16 12:41 ` Borislav Petkov
2022-08-16 16:51 ` Ashok Raj
2022-08-17 12:12 ` Ashok Raj
2022-08-17 14:23 ` Borislav Petkov
2022-08-17 15:29 ` Ashok Raj
2022-08-17 18:13 ` Borislav Petkov
2022-08-17 20:58 ` Ashok Raj
2022-08-17 21:56 ` Borislav Petkov
2022-08-18 9:58 ` Ashok Raj
2022-11-05 3:45 ` Ashok Raj [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=Y2XcRbaN9mDkWF9V@araj-dh-work \
--to=ashok_raj@linux.intel.com \
--cc=amc96@srcf.net \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stefantalpalaru@yahoo.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;
as well as URLs for NNTP newsgroup(s).