From: Peter Zijlstra <peterz@infradead.org>
To: Giovanni Gherdovich <ggherdovich@suse.cz>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@suse.de>,
Len Brown <lenb@kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
x86@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mel Gorman <mgorman@techsingularity.net>,
Doug Smythies <dsmythies@telus.net>,
Like Xu <like.xu@linux.intel.com>,
Neil Rickert <nwr10cst-oslnx@yahoo.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [PATCH 0/4] Frequency invariance fixes for x86
Date: Thu, 16 Apr 2020 09:20:17 +0200 [thread overview]
Message-ID: <20200416072017.GJ20730@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200416054745.740-1-ggherdovich@suse.cz>
On Thu, Apr 16, 2020 at 07:47:41AM +0200, Giovanni Gherdovich wrote:
> Patches 1-3 address bugs in the current frequency invariance support for x86,
> including the incompatibility with cpu0 hotplug reported by Chris Wilson at
> https://lore.kernel.org/lkml/158556634294.3228.4889951961483021094@build.alporthouse.com/
> and the issue with CPUs that have less than 4 cores pointed out earlier
> today by Like Xu at
> https://lore.kernel.org/lkml/20200416021210.170736-1-like.xu@linux.intel.com/
>
> Patch 4 is a minor code reorganization.
>
> Giovanni Gherdovich (3):
> x86, sched: Bail out of frequency invariance if base frequency is
> unknown
> x86, sched: Account for CPUs with less than 4 cores in freq.
> invariance
> x86, sched: Move check for CPU type to caller function
>
> Peter Zijlstra (Intel) (1):
> x86, sched: Don't enable static key when starting secondary CPUs
>
> arch/x86/kernel/smpboot.c | 47 +++++++++++++++++++++++++++++++++--------------
> 1 file changed, 33 insertions(+), 14 deletions(-)
Thanks!
prev parent reply other threads:[~2020-04-16 7:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 5:47 [PATCH 0/4] Frequency invariance fixes for x86 Giovanni Gherdovich
2020-04-16 5:47 ` [PATCH 1/4] x86, sched: Bail out of frequency invariance if base frequency is unknown Giovanni Gherdovich
2020-04-16 6:41 ` Giovanni Gherdovich
2020-04-16 15:41 ` Rafael J. Wysocki
2020-04-22 17:15 ` Ricardo Neri
2020-04-23 8:06 ` Giovanni Gherdovich
2020-04-24 1:32 ` Ricardo Neri
2020-04-24 5:53 ` Giovanni Gherdovich
2020-04-22 21:20 ` [tip: sched/urgent] " tip-bot2 for Giovanni Gherdovich
2020-04-16 5:47 ` [PATCH 2/4] x86, sched: Account for CPUs with less than 4 cores in freq. invariance Giovanni Gherdovich
2020-04-16 15:26 ` Dave Kleikamp
2020-04-22 21:20 ` [tip: sched/urgent] " tip-bot2 for Giovanni Gherdovich
2020-04-16 5:47 ` [PATCH 3/4] x86, sched: Don't enable static key when starting secondary CPUs Giovanni Gherdovich
2020-04-22 21:20 ` [tip: sched/urgent] " tip-bot2 for Peter Zijlstra (Intel)
2020-04-16 5:47 ` [PATCH 4/4] x86, sched: Move check for CPU type to caller function Giovanni Gherdovich
2020-04-22 21:20 ` [tip: sched/urgent] " tip-bot2 for Giovanni Gherdovich
2020-04-16 7:20 ` Peter Zijlstra [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=20200416072017.GJ20730@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@suse.de \
--cc=chris@chris-wilson.co.uk \
--cc=dsmythies@telus.net \
--cc=ggherdovich@suse.cz \
--cc=lenb@kernel.org \
--cc=like.xu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=nwr10cst-oslnx@yahoo.com \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.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 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).