mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Klaus Kusche <klaus.kusche@computerix.info>,
	Tim Chen <tim.c.chen@linux.intel.com>,
	"Chen, Yu C" <yu.c.chen@intel.com>
Cc: "Badole, Vishal" <Vishal.Badole@amd.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org,
	"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
	<x86@kernel.org>,
	platform-driver-x86@vger.kernel.org,
	K Prateek Nayak <KPrateek.Nayak@amd.com>,
	ricardo.neri@intel.com
Subject: Re: Cache-aware scheduling does not work well with amd big/little cores
Date: Mon, 31 Aug 2026 13:53:18 -0500	[thread overview]
Message-ID: <b8510d6e-4303-4698-a056-9f12cb859bc9@amd.com> (raw)
In-Reply-To: <3a8985e1-77b4-4127-af0a-ec1c397eb1ad@computerix.info>



On 8/31/26 13:49, Klaus Kusche wrote:
> 
> This would need some more testing efforts,
> because all my kernels are built without debugfs
> (using an earlier version of Mario's patch),
> and without Mario's patch and without debugfs,
> I don't get any big/little scheduling at all.
> So I'd need to build and test with debugfs
> (tomorrow I'm on a mountain tour, perhaps later this week).
> 
The debugfs patch doesn't really add anything tangible.  I'd say tests 
with that and debugfs turned off are just as valid as tests with no 
patch and debugfs turned on.

  reply	other threads:[~2026-08-31 18:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-29 15:42 Klaus Kusche
2026-08-31  1:53 ` Mario Limonciello
2026-08-31  2:08   ` Chen, Yu C
2026-08-31 11:24     ` Klaus Kusche
2026-08-31 17:29       ` Tim Chen
2026-08-31 18:49         ` Klaus Kusche
2026-08-31 18:53           ` Mario Limonciello [this message]
2026-09-05 15:40         ` Klaus Kusche

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=b8510d6e-4303-4698-a056-9f12cb859bc9@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=KPrateek.Nayak@amd.com \
    --cc=Vishal.Badole@amd.com \
    --cc=klaus.kusche@computerix.info \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=ricardo.neri@intel.com \
    --cc=tim.c.chen@linux.intel.com \
    --cc=x86@kernel.org \
    --cc=yu.c.chen@intel.com \
    /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®