From: Atish Patra <Atish.Patra@wdc.com>
To: "paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"sudeep.holla@arm.com" <sudeep.holla@arm.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"rafael@kernel.org" <rafael@kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"palmer@sifive.com" <palmer@sifive.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"rfontana@redhat.com" <rfontana@redhat.com>,
"mchehab+samsung@kernel.org" <mchehab+samsung@kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"morten.rasmussen@arm.com" <morten.rasmussen@arm.com>,
"robh@kernel.org" <robh@kernel.org>,
"anup@brainfault.org" <anup@brainfault.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"mingo@kernel.org" <mingo@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"Jonathan.Cameron@huawei.com" <Jonathan.Cameron@huawei.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ottosabart@seberm.com" <ottosabart@seberm.com>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH v7 1/7] Documentation: DT: arm: add support for sockets defining package boundaries
Date: Thu, 27 Jun 2019 19:58:50 +0000 [thread overview]
Message-ID: <513883349e80792884b3754c259357d8066ad348.camel@wdc.com> (raw)
In-Reply-To: <873a80f0-e704-dd7e-4db9-b159b23847fc@wdc.com>
On Wed, 2019-06-26 at 19:18 -0700, Atish Patra wrote:
> On 6/26/19 5:31 PM, Paul Walmsley wrote:
> > Hi Sudeep, Atish,
> >
> > On Mon, 17 Jun 2019, Atish Patra wrote:
> >
> > > From: Sudeep Holla <sudeep.holla@arm.com>
> > >
> > > The current ARM DT topology description provides the operating
> > > system
> > > with a topological view of the system that is based on leaf nodes
> > > representing either cores or threads (in an SMT system) and a
> > > hierarchical set of cluster nodes that creates a hierarchical
> > > topology
> > > view of how those cores and threads are grouped.
> > >
> > > However this hierarchical representation of clusters does not
> > > allow to
> > > describe what topology level actually represents the physical
> > > package or
> > > the socket boundary, which is a key piece of information to be
> > > used by
> > > an operating system to optimize resource allocation and
> > > scheduling.
> > >
> > > Lets add a new "socket" node type in the cpu-map node to describe
> > > the
> > > same.
> > >
> > > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> > > Reviewed-by: Rob Herring <robh@kernel.org>
> >
> > This one doesn't apply cleanly here on top of v5.2-rc2, Linus's
> > master
> > branch, and next-20190626. The reject file is below. Am I missing
> > a patch?
> >
>
> That's weird. I could apply the patch from any git tree (github or
> git.kernel.org) but not from mail or patchworks.
>
> git log doesn't show any recent modifications of that file. I am
> trying
> to figure out what's wrong.
The space changes in this patch caused the conflict. The patch was
generated with -b which was suggested during the initial review.
I should removed it before sending v7. My bad.
I have fixed that and sent a v8 that should be cleanly applied on
latest master. The patch series is also available at
https://github.com/atishp04/linux/tree/5.2-rc6_topology
Regards,
Atish
> > - Paul
> >
> > --- Documentation/devicetree/bindings/arm/topology.txt
> > +++ Documentation/devicetree/bindings/arm/topology.txt
> > @@ -185,13 +206,15 @@ Bindings for cluster/cpu/thread nodes are
> > defined as follows:
> > 4 - Example dts
> > ===========================================
> >
> > -Example 1 (ARM 64-bit, 16-cpu system, two clusters of clusters):
> > +Example 1 (ARM 64-bit, 16-cpu system, two clusters of clusters in
> > a single
> > +physical socket):
> >
> > cpus {
> > #size-cells = <0>;
> > #address-cells = <2>;
> >
> > cpu-map {
> > + socket0 {
> > cluster0 {
> > cluster0 {
> > core0 {
> >
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-27 19:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 18:59 [PATCH v7 0/7] Unify CPU topology across ARM & RISC-V Atish Patra
2019-06-17 18:59 ` [PATCH v7 1/7] Documentation: DT: arm: add support for sockets defining package boundaries Atish Patra
2019-06-27 0:31 ` Paul Walmsley
2019-06-27 2:18 ` Atish Patra
2019-06-27 19:58 ` Atish Patra [this message]
2019-06-17 18:59 ` [PATCH v7 2/7] dt-binding: cpu-topology: Move cpu-map to a common binding Atish Patra
2019-06-17 18:59 ` [PATCH v7 3/7] cpu-topology: Move cpu topology code to common code Atish Patra
2019-06-19 17:38 ` Greg Kroah-Hartman
2019-06-21 22:31 ` Atish Patra
2019-06-23 17:51 ` Paul Walmsley
2019-06-17 18:59 ` [PATCH v7 4/7] arm: Use common cpu_topology structure and functions Atish Patra
2019-06-19 12:10 ` Sudeep Holla
2019-06-24 15:06 ` Sudeep Holla
2019-06-24 15:30 ` Russell King - ARM Linux admin
2019-06-24 15:33 ` Sudeep Holla
2019-06-17 18:59 ` [PATCH v7 5/7] RISC-V: Parse cpu topology during boot Atish Patra
2019-06-17 18:59 ` [PATCH v7 6/7] base: arch_topology: update Kconfig help description Atish Patra
2019-06-17 18:59 ` [PATCH v7 7/7] MAINTAINERS: Add an entry for generic architecture topology Atish Patra
2019-06-19 17:37 ` Greg Kroah-Hartman
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=513883349e80792884b3754c259357d8066ad348.camel@wdc.com \
--to=atish.patra@wdc.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=ottosabart@seberm.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rfontana@redhat.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).