From: Len Brown <lenb@kernel.org>
To: tglx@linutronix.de, venkatesh.pallipadi@intel.com
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
stable@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, Jeff Chua <jeff.chua.linux@gmail.com>
Subject: send_IPI_mask_bitmask() (Re: 2.6.21 known regressions (v2) (for -stable team))
Date: Sun, 29 Apr 2007 01:34:38 -0400 [thread overview]
Message-ID: <200704290134.39048.lenb@kernel.org> (raw)
In-Reply-To: <1177779533.7646.264.camel@localhost.localdomain>
On Saturday 28 April 2007 12:58, Thomas Gleixner wrote:
> On Sat, 2007-04-28 at 18:27 +0200, Michal Piotrowski wrote:
> > Hi all,
> >
> > Here is a list of known regressions reported after 2.6.21 release.
>
> Michal, thanks for stepping up !
>
> > Subject : 2.6.21 - BUG: at arch/i386/kernel/smp.c:177 send_IPI_mask_bitmask()
> > References : http://lkml.org/lkml/2007/4/27/621
> > Submitter : Jeff Chua <jeff.chua.linux@gmail.com>
> > Status : unknown
>
> Len,
>
> clockevents_notify() is called with the power verify information for an
> offline CPU. I can handle this in the clockevents code, but I think acpi
> is the correct place.
So the CONFIG_GENERIC_CLOCKEVENTS=y case is broken,
but the CONFIG_GENERIC_CLOCKEVENTS=n below is okay?
Not immediately clear why both cases can't fail.
Maybe Venki can explain.
-Len
static void acpi_propagate_timer_broadcast(struct acpi_processor *pr)
{
#ifdef CONFIG_GENERIC_CLOCKEVENTS
unsigned long reason;
reason = pr->power.timer_broadcast_on_state < INT_MAX ?
CLOCK_EVT_NOTIFY_BROADCAST_ON : CLOCK_EVT_NOTIFY_BROADCAST_OFF;
clockevents_notify(reason, &pr->id);
#else
cpumask_t mask = cpumask_of_cpu(pr->id);
if (pr->power.timer_broadcast_on_state < INT_MAX)
on_each_cpu(switch_APIC_timer_to_ipi, &mask, 1, 1);
else
on_each_cpu(switch_ipi_to_APIC_timer, &mask, 1, 1);
#endif
}
next prev parent reply other threads:[~2007-04-29 5:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 16:27 2.6.21 known regressions (v2) (for -stable team) Michal Piotrowski
2007-04-28 16:27 ` Michal Piotrowski
2007-04-28 16:52 ` Gene Heskett
2007-04-28 17:18 ` Michal Piotrowski
2007-04-28 17:18 ` Michal Piotrowski
2007-04-28 17:52 ` Gene Heskett
2007-04-28 17:52 ` Gene Heskett
2007-04-28 18:19 ` [stable] " Greg KH
2007-04-28 18:19 ` Greg KH
2007-04-28 21:21 ` Krzysztof Halasa
2007-04-28 21:21 ` Krzysztof Halasa
2007-04-28 21:21 ` Krzysztof Halasa
2007-04-29 1:25 ` Greg KH
2007-04-29 1:25 ` Greg KH
2007-04-29 1:25 ` Greg KH
2007-04-28 16:58 ` Thomas Gleixner
2007-04-29 5:34 ` Len Brown [this message]
2007-04-29 8:25 ` send_IPI_mask_bitmask() (Re: 2.6.21 known regressions (v2) (for -stable team)) Thomas Gleixner
2007-04-28 17:06 ` 2.6.21 known regressions (v2) (for -stable team) Thomas Gleixner
2007-04-28 18:10 ` Thomas Meyer
2007-04-28 20:04 ` Thomas Gleixner
2007-04-28 18:03 ` Thomas Meyer
2007-04-28 19:06 ` Diego Calleja
2007-04-28 19:06 ` Diego Calleja
2007-04-30 21:30 ` Stephen Hemminger
2007-04-30 22:35 ` Håkan Lindqvist
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=200704290134.39048.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@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.