From: Ingo Molnar <mingo@elte.hu>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "ego@in.ibm.com" <ego@in.ibm.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"a.p.zijlstra@chello.nl" <a.p.zijlstra@chello.nl>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:sched/urgent] sched: Print sched_group::__cpu_power in sched_domain_debug
Date: Tue, 14 Apr 2009 20:40:07 +0200 [thread overview]
Message-ID: <20090414184007.GB11214@elte.hu> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA39B3CF3B4@orsmsx505.amr.corp.intel.com>
* Luck, Tony <tony.luck@intel.com> wrote:
> - printk(KERN_CONT " %s (__cpu_power = %d)", str,
> + printk(KERN_CONT " %s", str);
> + if (group->__cpu_power != SCHED_LOAD_SCALE)
> + printk(KERN_CONT " (__cpu_power = %d)",
> group->__cpu_power);
>
> That looks better.
>
> Acked-by: Tony Luck <tony.luck@intel.com>
Thanks, picked up this variant!
Ingo
next prev parent reply other threads:[~2009-04-14 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 4:55 [PATCH] " Gautham R Shenoy
2009-03-30 4:55 ` Gautham R Shenoy
2009-04-01 16:03 ` [tip:sched/urgent] " Gautham R Shenoy
2009-04-13 18:53 ` Tony Luck
2009-04-14 0:09 ` Ingo Molnar
2009-04-14 3:39 ` Gautham R Shenoy
2009-04-14 12:03 ` [tip:sched/urgent] sched: Avoid printing sched_group::__cpu_power for default case tip-bot for Gautham R Shenoy
2009-04-14 16:29 ` [tip:sched/urgent] sched: Print sched_group::__cpu_power in sched_domain_debug Luck, Tony
2009-04-14 17:06 ` Gautham R Shenoy
2009-04-14 17:18 ` Luck, Tony
2009-04-14 18:40 ` Ingo Molnar [this message]
2009-04-14 18:42 ` [tip:sched/urgent] sched: Avoid printing sched_group::__cpu_power for default case tip-bot for Gautham R Shenoy
2009-04-16 22:48 ` tip-bot for Gautham R Shenoy
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=20090414184007.GB11214@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=ego@in.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®