mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Graf (AWS), Alexander" <graf@amazon.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Reinette Chatre <reinette.chatre@intel.com>,
	Dave Martin <Dave.Martin@arm.com>,
	James Morse <james.morse@arm.com>,
	Babu Moger <babu.moger@amd.com>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H . Peter Anvin" <hpa@zytor.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"nh-open-source@amazon.com" <nh-open-source@amazon.com>,
	"Elshahed, Ibrahim" <lshahed@amazon.de>,
	"Wise, Jasper" <jaspwise@amazon.co.uk>
Subject: Re: [PATCH] x86/resctrl: Require force for L3 CAT on early Skylake-X
Date: Thu, 15 Oct 2026 21:38:05 +0000	[thread overview]
Message-ID: <0115c4f1-bc65-49e9-ab5f-9c044e9cfcf6@amazon.de> (raw)
In-Reply-To: <atEJRr6iJhZv9lvU@agluck-desk3>

Hi Tony,

On 15.10.26 19:11, Luck, Tony wrote:
> On Thu, Oct 15, 2026 at 04:58:46PM +0000, Graf (AWS), Alexander wrote:
>> I ran a few more experiments. This seems un- or if anything only mildly
>> related to kexec. The real culprit is the microcode version. In my
>> environment, we boot with older microcode (0x1000159), then hot load the
>> latest microcode (0x1000191) and then kexec. In that flow, any write to
>> IA32_L3_QOS_MASK_n stalls the socket that write happens on. I'm
>> collecting a bit more data - including microcode version bisects, early
>> load, etc - and give you a full rundown tomorrow or on Monday, depending
>> on how quickly it finishes.
> Alexander,
>
> I don't think that an upstream generic kernel solution is the right
> path for your very system-specific issue.
>
> Can't you fix your deployment scripts to look at system stepping and
> use that to choose the kernel boot options? I presume that you already
> have checks for CPU model number since there are lots of different
> options appropriate on a per-model basis. So adding a stepping check
> may be easier than battling upstream Linux submission process.


I can hack around it for my specific environment. The reason I'm 
submitting this is because I expect that I won't be the only person 
falling into that pitfall. I expect that early microcode loading (which 
is distro default) would show the same failure without kexec. I want to 
save the next person that runs into it the same painful debugging 
exercise :).


Alex

      reply	other threads:[~2026-10-15 21:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  8:36 Alexander Graf
2026-10-14 16:16 ` Luck, Tony
2026-10-14 20:44 ` Reinette Chatre
2026-10-15 16:58   ` Graf (AWS), Alexander
2026-10-15 17:11     ` Luck, Tony
2026-10-15 21:38       ` Graf (AWS), Alexander [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=0115c4f1-bc65-49e9-ab5f-9c044e9cfcf6@amazon.de \
    --to=graf@amazon.de \
    --cc=Dave.Martin@arm.com \
    --cc=babu.moger@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=jaspwise@amazon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lshahed@amazon.de \
    --cc=mingo@redhat.com \
    --cc=nh-open-source@amazon.com \
    --cc=reinette.chatre@intel.com \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.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

all inboxes | Powered by JetHome®