All of lore.kernel.org
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] arm64: topology: Implement basic CPU topology support
Date: Tue, 17 Dec 2013 11:47:34 +0000	[thread overview]
Message-ID: <20131217114734.GC32118@arm.com> (raw)
In-Reply-To: <20131216151232.GH3185@sirena.org.uk>

On Mon, Dec 16, 2013 at 03:12:32PM +0000, Mark Brown wrote:
> On Mon, Dec 16, 2013 at 02:46:38PM +0000, Lorenzo Pieralisi wrote:
> > On Mon, Dec 16, 2013 at 12:29:48PM +0000, Mark Brown wrote:
> [MPIDR parsing]
> > > Again, this is gone from the current version.  Like I said to Catalin it
> > > does feel like this is making more work for systems that have done the
> > > right thing with their MPIDRs which doesn't seem ideal (and note that
> > > all the DTs that you guys are publishing for your models lack any
> > > topology information at present).
> 
> > This is an age-old question and the problem has always been that the
> > "right thing" is recommended, not enforced. I do not want to turn this into
> > bikeshedding, as long as cpu-map node takes priority if present, fine by me.
> 
> I already dropped that code, though I could resurrect it (perhaps as a
> separate patch).  The way the code was written was as you describe as a
> last resort - MPIDR would only be considered if the explict topology
> binding was not present, it was done as a last step before reporting if
> no other topology information was discovered.
> 
> Actually now I think about it if we're not going to parse the MPIDR we
> should probably update the bindings to say that the topology binding is
> mandatory for any v8 system with more than one core.

Do we need such information if only a flat topology is needed?

-- 
Catalin

  reply	other threads:[~2013-12-17 11:47 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 13:13 [PATCH 1/6] arm64: Add asm/cpu.h Mark Brown
2013-12-11 13:13 ` [PATCH 2/6] arm64: dts: Add a virtio disk to the RTSM motherboard Mark Brown
2013-12-11 13:13 ` [PATCH 3/6] arm64: dts: Add a devicetree for the ARMv8 4xA53 4xA57 FVP Mark Brown
2013-12-11 13:55   ` Mark Rutland
2013-12-11 14:11     ` Mark Brown
2013-12-11 15:04       ` Mark Rutland
2013-12-11 16:00         ` Mark Brown
2013-12-11 16:08         ` Jon Medhurst (Tixy)
2013-12-11 16:41           ` Ryan Harkin
2013-12-11 17:09             ` Mark Rutland
2013-12-11 17:50               ` Mark Brown
2013-12-11 13:13 ` [PATCH 4/6] arm64: topology: Implement basic CPU topology support Mark Brown
2013-12-11 14:12   ` Will Deacon
2013-12-11 14:15     ` Mark Brown
2013-12-11 14:24       ` Catalin Marinas
2013-12-11 14:30         ` Mark Brown
2013-12-11 14:49           ` Catalin Marinas
2013-12-11 16:13             ` Mark Brown
2013-12-12  6:59         ` Hanjun Guo
2013-12-12 10:27           ` Mark Brown
2013-12-12 11:22             ` Hanjun Guo
2013-12-16 10:57   ` Lorenzo Pieralisi
2013-12-16 11:33     ` Mark Brown
2013-12-16 12:29     ` Mark Brown
2013-12-16 14:46       ` Lorenzo Pieralisi
2013-12-16 15:12         ` Mark Brown
2013-12-17 11:47           ` Catalin Marinas [this message]
2013-12-17 12:17             ` Mark Brown
2013-12-16 14:45   ` Alex Shi
2013-12-16 15:22     ` Mark Brown
2013-12-17  7:19       ` Alex Shi
2013-12-17 12:02         ` Mark Brown
2013-12-11 13:13 ` [PATCH 5/6] arm64: topology: Tell the scheduler about the relative power of cores Mark Brown
2013-12-11 14:47   ` Catalin Marinas
2013-12-11 17:31     ` Mark Brown
2013-12-11 19:27       ` Nicolas Pitre
2013-12-12 11:56         ` Morten Rasmussen
2013-12-12 12:22           ` Mark Brown
2013-12-12 13:42             ` Morten Rasmussen
2013-12-12 14:26           ` Vincent Guittot
2013-12-11 13:13 ` [PATCH 6/6] arm64: dts: Add CPU topology properties for ARMv8 4xA53 4xA57 FVP Mark Brown
2013-12-11 14:10 ` [PATCH 1/6] arm64: Add asm/cpu.h Catalin Marinas
2013-12-11 14:23   ` Mark Brown
2013-12-11 14:27     ` Catalin Marinas
2013-12-12  6:50       ` Hanjun Guo
2013-12-12 10:36         ` Mark Rutland
2013-12-12 11:20           ` Hanjun Guo

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=20131217114734.GC32118@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.