From: Alex Shi <alex.shi@intel.com>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Alex Shi <lkml.alex@gmail.com>,
mingo@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
santosh.shilimkar@ti.com, tglx@linutronix.de, "Chen,
Tim C" <tim.c.chen@intel.com>
Subject: Re: [tip:timers/urgent] clockevents: tTack broadcast device mode change in tick_broadcast_switch_to_oneshot()
Date: Thu, 12 Apr 2012 13:10:11 +0800 [thread overview]
Message-ID: <4F8663B3.9060900@intel.com> (raw)
In-Reply-To: <1334205354.2583.1.camel@sbsiddha-mobl2>
On 04/12/2012 12:35 PM, Suresh Siddha wrote:
> On Thu, 2012-04-12 at 09:27 +0800, Alex Shi wrote:
>> This patch recovered the loopback netperf testing on NHM machine, but
>> on SNB machine, It isn't need a broadcost timer at all.
>>
>> Do you think it is better to remove oneshot broadcast on WSM/SNB machine?
>
> on WSM/SNB, we already don't use broadcast timer and always use
> apictimer instead.
Yes, you are right. I omitted this.
Tick Device: mode: 1
Broadcast device
Clock Event Device: hpet
...
tick_broadcast_mask: 00000000
tick_broadcast_oneshot_mask: 00000000
>
> thanks,
> suresh
>
next prev parent reply other threads:[~2012-04-12 5:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 6:03 [PATCH] clockevents: Leave broadcast device shtudown only if the current device is always running Santosh Shilimkar
2012-04-09 22:41 ` Suresh Siddha
2012-04-10 6:56 ` Shilimkar, Santosh
2012-04-10 9:49 ` [tip:timers/urgent] clockevents: tTack broadcast device mode change in tick_broadcast_switch_to_oneshot() tip-bot for Suresh Siddha
2012-04-12 1:27 ` Alex Shi
2012-04-12 4:35 ` Suresh Siddha
2012-04-12 5:10 ` Alex Shi [this message]
[not found] ` <CA++bM2th5XW1gxrHbcHwDK=qBBaNc3ut0ydbNNStfNa-Xa-9tA@mail.gmail.com>
2012-04-11 6:34 ` [PATCH] clockevents: Leave broadcast device shtudown only if the current device is always running Feng Tang
2012-04-11 10:10 ` Thomas Gleixner
2012-04-11 16:04 ` Feng Tang
2012-04-11 21:01 ` Suresh Siddha
2012-04-15 12:57 ` Santosh Shilimkar
2012-04-16 22:03 ` Suresh Siddha
2012-04-17 8:14 ` Santosh Shilimkar
2012-04-17 19:11 ` Suresh Siddha
2012-04-18 5:41 ` Shilimkar, Santosh
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=4F8663B3.9060900@intel.com \
--to=alex.shi@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml.alex@gmail.com \
--cc=mingo@kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@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 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.