All of lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64: topology: Implement basic CPU topology support
Date: Thu, 12 Dec 2013 10:22:14 +0000	[thread overview]
Message-ID: <20131212102214.GE11044@sirena.org.uk> (raw)
In-Reply-To: <52A96201.509@linaro.org>

On Thu, Dec 12, 2013 at 03:13:05PM +0800, Hanjun Guo wrote:

> The scheduler already used topology and cache sharing when
> CONFIG_SCHED_MC and/or CONFIG_SCHED_SMT are enable. can you
> add these configs for arm64 so the scheduler can use it?
> something like:

Right, yes - these should be added.  They got mistakenly included in the
patch for GTS which is obviously out of tree.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131212/bf0e1d68/attachment.sig>

      reply	other threads:[~2013-12-12 10:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 20:00 [PATCH 1/3] arm64: topology: Implement basic CPU topology support Mark Brown
2013-12-11 20:00 ` [PATCH 2/3] arm64: topology: Tell the scheduler about the relative power of cores Mark Brown
2013-12-12 11:35   ` Morten Rasmussen
2013-12-12 12:06     ` Mark Brown
2013-12-12 13:36       ` Morten Rasmussen
2013-12-12 17:39         ` Catalin Marinas
2013-12-12 18:06           ` Mark Brown
2013-12-11 20:00 ` [PATCH 3/3] arm64: topology: Add support for topology DT bindings Mark Brown
2013-12-12  7:13 ` [PATCH 1/3] arm64: topology: Implement basic CPU topology support Hanjun Guo
2013-12-12 10:22   ` Mark Brown [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=20131212102214.GE11044@sirena.org.uk \
    --to=broonie@kernel.org \
    --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.