From: Thomas Gleixner <tglx@linutronix.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix dynticks for voyager
Date: Tue, 01 May 2007 00:13:10 +0200 [thread overview]
Message-ID: <1177971190.5791.251.camel@localhost.localdomain> (raw)
In-Reply-To: <1177951131.3674.37.camel@mulgrave.il.steeleye.com>
On Mon, 2007-04-30 at 11:38 -0500, James Bottomley wrote:
> As usual voyager tripped over an explicit boot CPU is zero assumption in
> the dynticks code. This is the fix I have queued in the voyager tree.
I expected some kind of voyager breakage. I desperately tried to find
one for testing in my museum of bizarre hardware to avoid this,
but ... :)
tglx
> ---
>
> >From 5d3e489cf8fcf12eff92476098b9bfa0120ee3c7 Mon Sep 17 00:00:00 2001
> From: James Bottomley <James.Bottomley@HansenPartnership.com>
> Date: Mon, 30 Apr 2007 11:27:25 -0500
> Subject: [VOYAGER] clockevents: correct boot cpu is zero assumption
>
> This isn't true for voyager, so alter setup_pit_timer() to initialise
> the cpumask from the current processor id (which should be the boot
> processor) rather than defaulting to zero.
>
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
> ---
> arch/i386/kernel/i8253.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/i386/kernel/i8253.c b/arch/i386/kernel/i8253.c
> index 10cef5c..f8a3c40 100644
> --- a/arch/i386/kernel/i8253.c
> +++ b/arch/i386/kernel/i8253.c
> @@ -110,7 +110,7 @@ void __init setup_pit_timer(void)
> * Start pit with the boot cpu mask and make it global after the
> * IO_APIC has been initialized.
> */
> - pit_clockevent.cpumask = cpumask_of_cpu(0);
> + pit_clockevent.cpumask = cpumask_of_cpu(smp_processor_id());
> pit_clockevent.mult = div_sc(CLOCK_TICK_RATE, NSEC_PER_SEC, 32);
> pit_clockevent.max_delta_ns =
> clockevent_delta2ns(0x7FFF, &pit_clockevent);
next prev parent reply other threads:[~2007-04-30 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 16:38 [PATCH] fix dynticks for voyager James Bottomley
2007-04-30 22:13 ` Thomas Gleixner [this message]
2007-05-01 22:24 ` Matt Mackall
2007-05-02 0:26 ` Jeremy Fitzhardinge
2007-05-02 0:47 ` James Bottomley
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=1177971190.5791.251.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.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 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.