mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Reinette Chatre <reinette.chatre@intel.com>
To: Alexander Graf <graf@amazon.com>, Tony Luck <tony.luck@intel.com>
Cc: 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>,
	<linux-kernel@vger.kernel.org>, <nh-open-source@amazon.com>,
	<lshahed@amazon.de>, <jaspwise@amazon.co.uk>
Subject: Re: [PATCH] x86/resctrl: Require force for L3 CAT on early Skylake-X
Date: Wed, 14 Oct 2026 13:44:15 -0700	[thread overview]
Message-ID: <4bc68d06-a45f-45cc-80a4-f72806d5c976@intel.com> (raw)
In-Reply-To: <20261014083637.65430-1-graf@amazon.com>

Hi Alexander,

On 10/14/26 1:36 AM, Alexander Graf wrote:
> When L3 CAT gets enabled with rdt=l3cat on Skylake-X stepping 3,
> consecutive kexec boots hang for me during secondary socket bringup.
> Cold boots on the same machine work.

Any insight into where the hang occurs?

What is state of resctrl fs when kexec runs? Is it mounted (with which options)?

Does the boot hang whether resctrl fs is mounted or not?

If resctrl is mounted at time of kexec, has it been set up with different groups?
Does kexec task run from a particular group?
 
Does it make a difference if resctrl fs is unmounted before kexec? As I understand
kexec takes system from resctrl without giving opportunity to reset. There should
be no accumulation of state but system may boot up with settings left over from
previous run. Unmounting resctrl would give opportunity to reset state so that
new kernel can start with clean slate.

What does "during secondary socket bringup" mean exactly? For example, is
the hang when first CPU of second socket is onlined and found to be hanging
in the resctrl online handler?

Thank you.

Reinette




      parent reply	other threads:[~2026-10-14 20:44 UTC|newest]

Thread overview: 3+ 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 [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=4bc68d06-a45f-45cc-80a4-f72806d5c976@intel.com \
    --to=reinette.chatre@intel.com \
    --cc=Dave.Martin@arm.com \
    --cc=babu.moger@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=graf@amazon.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=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®