linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: smp: Allow real broadcast device selection instead of always dummy
Date: Wed, 13 Mar 2013 21:07:01 +0530	[thread overview]
Message-ID: <51409D1D.9000500@ti.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1303131516090.22263@ionos>

On Wednesday 13 March 2013 07:49 PM, Thomas Gleixner wrote:
> On Wed, 13 Mar 2013, Santosh Shilimkar wrote:
>> On Wednesday 13 March 2013 02:36 PM, Santosh Shilimkar wrote:
>>> With recent arm broadcast time clean-up from Mark Rutland, the dummy
>>> broadcast device is always registered with timer subsystem. And since
>>> the rating of the dummy clock event is very high, it is preferred
>>> over a real broad-cast clock event.
>>>
>>> This is a change in behavior from past and not an intended
>>> one. So reduce the rating of the dummy clockevent so that
>>> real broadcast device is selected when available.
>>>
>>> Without this all the C states with C3STOP won't work since
>>> the broad cast notifier will take an abort.
>>>
>>> Cc: Mark Rutland <mark.rutland@arm.com>
>>> Cc: Russell King <linux@arm.linux.org.uk>
>>>
>>> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>>> ---
>>> Its a regression so hopefully can get into the 3.9-rcx. Noticed
>>> this one on A15 platform. A9 platform the issue may not be seen
>>> since the local timer check avoids dummy timer registration.
>>>
>> Some one pointed me to a fix made by Mark which was discussed
>> under '[BUG] ARM Architected timers appear broken in 3.9-rc1' subject.
>> That patch seems to be more of work around since the root of the
>> problem is incorrect dummy timer rating. Either way, both patches
>> fix the issue.
> 
> Well, using a dummy timer as the broadcast event device is a bug, no
> matter what the rating is. The fix is in Linus tree already.
>
Agree.
 
> Though making the rating of the dummy lower is definitely a good
> thing, so a real hardware device which is detected later can replace
> the dummy device. So yes, the rating should be low for the dummy
> timer.
> 
Exactly. As Mark pointed out, you have already applied Mark's patch.
I was just wondering whether you can take the $subject patch as well
with ack from Russell, Mark.

Regards,
Santosh

  reply	other threads:[~2013-03-13 15:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13  9:06 [PATCH] ARM: smp: Allow real broadcast device selection instead of always dummy Santosh Shilimkar
2013-03-13  9:28 ` Santosh Shilimkar
2013-03-13 10:16   ` Mark Rutland
2013-03-13 11:24     ` Santosh Shilimkar
2013-03-13 12:25       ` Mark Rutland
2013-03-13 15:44         ` Santosh Shilimkar
2013-03-13 16:18           ` Mark Rutland
2013-03-14  7:45             ` Santosh Shilimkar
2013-03-14  8:50               ` Thomas Gleixner
2013-03-14 10:28               ` Mark Rutland
2013-03-14 10:46                 ` Santosh Shilimkar
2013-03-14 19:41                 ` Stephen Boyd
2013-03-13 14:19   ` Thomas Gleixner
2013-03-13 15:37     ` Santosh Shilimkar [this message]
2013-03-13 18:31       ` Thomas Gleixner
2013-03-14  6:09         ` Santosh Shilimkar

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=51409D1D.9000500@ti.com \
    --to=santosh.shilimkar@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).