All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Diwakar Tundlam <dtundlam@nvidia.com>
Cc: "'Ingo Molnar'" <mingo@kernel.org>,
	"'Andrew Morton'" <akpm@linux-foundation.org>,
	"'Christoph Lameter'" <cl@gentwo.org>,
	"'Michael Neuling'" <mikey@neuling.org>,
	"'Stephen Rothwell'" <sfr@canb.auug.org.au>,
	"'Benjamin Herrenschmidt'" <benh@kernel.crashing.org>,
	"'David Rientjes'" <rientjes@google.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	Peter De Schrijver <pdeschrijver@nvidia.com>
Subject: RE: [PATCH] sched: Enable arch-specific asym packing option in sched domain
Date: Sat, 05 May 2012 22:35:17 +0200	[thread overview]
Message-ID: <1336250117.2463.140.camel@laptop> (raw)
In-Reply-To: <1DD7BFEDD3147247B1355BEFEFE46652379C3DF103@HQMAIL04.nvidia.com>

On Fri, 2012-05-04 at 16:18 -0700, Diwakar Tundlam wrote:
> 
> Yes, this is for Nvidia's ARM Quad-core Tegra CPU. It is a single package, organized flatly.

Then you don't want to poke at SD_CPU_INIT since thats across packages.


  parent reply	other threads:[~2012-05-05 20:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 20:28 [PATCH] sched: Enable arch-specific asym packing option in sched domain Diwakar Tundlam
2012-05-04 21:17 ` Peter Zijlstra
2012-05-04 22:06 ` Diwakar Tundlam
2012-05-04 22:10   ` Peter Zijlstra
2012-05-04 22:18     ` Diwakar Tundlam
2012-05-04 22:29       ` Peter Zijlstra
2012-05-04 23:18         ` Diwakar Tundlam
2012-05-04 23:20           ` Michael Neuling
2012-05-04 23:25             ` Diwakar Tundlam
2012-05-04 23:41               ` Michael Neuling
2012-05-07  2:59               ` Michael Wang
2012-05-04 23:55           ` Suresh Siddha
2012-05-05 20:35           ` Peter Zijlstra [this message]
2012-05-07 17:25             ` Diwakar Tundlam
2012-05-08  9:46               ` Peter Zijlstra
2012-05-04 22:47       ` Michael Neuling
2012-05-04 22:51       ` Michael Neuling

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=1336250117.2463.140.camel@laptop \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=cl@gentwo.org \
    --cc=dtundlam@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikey@neuling.org \
    --cc=mingo@kernel.org \
    --cc=pdeschrijver@nvidia.com \
    --cc=rientjes@google.com \
    --cc=sfr@canb.auug.org.au \
    /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.