From: Peter Zijlstra <peterz@infradead•org>
To: Qing Wang <wangqing@vivo•com>
Cc: Juri Lelli <juri.lelli@redhat•com>,
"Rafael J. Wysocki" <rafael@kernel•org>,
Catalin Marinas <catalin.marinas@arm•com>,
Ben Segall <bsegall@google•com>,
Paul Mackerras <paulus@samba•org>,
"H. Peter Anvin" <hpa@zytor•com>, Will Deacon <will@kernel•org>,
Vincent Guittot <vincent.guittot@linaro•org>,
x86@kernel•org, Ingo Molnar <mingo@redhat•com>,
Mel Gorman <mgorman@suse•de>,
linuxppc-dev@lists•ozlabs.org,
Steven Rostedt <rostedt@goodmis•org>,
Borislav Petkov <bp@alien8•de>,
Thomas Gleixner <tglx@linutronix•de>,
Dietmar Eggemann <dietmar.eggemann@arm•com>,
linux-arm-kernel@lists•infradead.org,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
linux-kernel@vger•kernel.org, Sudeep Holla <sudeep.holla@arm•com>,
Daniel Bristot de Oliveira <bristot@redhat•com>
Subject: Re: [PATCH 1/3] sched: topology: add input parameter for sched_domain_flags_f()
Date: Tue, 29 Mar 2022 11:23:30 +0200 [thread overview]
Message-ID: <20220329092330.GG8939@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <1648545322-14531-2-git-send-email-wangqing@vivo.com>
On Tue, Mar 29, 2022 at 02:15:19AM -0700, Qing Wang wrote:
> From: Wang Qing <wangqing@vivo•com>
>
> sched_domain_flags_f() are statically set now, but actually, we can get a lot
> of necessary information based on the cpu_map. e.g. we can know whether its
> cache is shared.
>
> Allows custom extension without affecting current.
Still NAK
next prev parent reply other threads:[~2022-03-29 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 9:15 [PATCH 0/3] support for describing cache topology from DT Qing Wang
2022-03-29 9:15 ` [PATCH 1/3] sched: topology: add input parameter for sched_domain_flags_f() Qing Wang
2022-03-29 9:23 ` Peter Zijlstra [this message]
2022-03-29 9:15 ` [PATCH 2/3] arch_topology: support for describing cache topology from DT Qing Wang
2022-03-29 9:15 ` [PATCH 3/3] arm64: add arm64 default topology Qing Wang
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=20220329092330.GG8939@worktop.programming.kicks-ass.net \
--to=peterz@infradead$(echo .)org \
--cc=bp@alien8$(echo .)de \
--cc=bristot@redhat$(echo .)com \
--cc=bsegall@google$(echo .)com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=dietmar.eggemann@arm$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=juri.lelli@redhat$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mgorman@suse$(echo .)de \
--cc=mingo@redhat$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=rafael@kernel$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
--cc=sudeep.holla@arm$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=vincent.guittot@linaro$(echo .)org \
--cc=wangqing@vivo$(echo .)com \
--cc=will@kernel$(echo .)org \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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