From: Thomas Gleixner <tglx@linutronix.de>
To: Thomas Renninger <trenn@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>,
"andreas.herrmann3" <andreas.herrmann3@amd.com>,
Richard <tuxbox.guru@gmail.com>,
eumaster@gmail.com, uli.geins@geins-web.de
Subject: Re: [PATCH] Re: AMD Mobile Semprons (3500+, 3600+,...) break with nohz and highres enabled
Date: Wed, 16 Jul 2008 21:03:12 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.1.10.0807162100380.4316@apollo.tec.linutronix.de> (raw)
In-Reply-To: <200807161827.16898.trenn@suse.de>
On Wed, 16 Jul 2008, Thomas Renninger wrote:
> This is against Andi's (ak) release branch,
> hope that is ok...
No idea what that is.
> Can this one be reviewed/added, pls.
Reviewed yes. Added no.
> kernel/time/tick-sched.c | 31 +++++++++++++++++++++++++++++++
> 1 files changed, 31 insertions(+), 0 deletions(-)
>
> diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> index b854a89..bda0164 100644
> --- a/kernel/time/tick-sched.c
> +++ b/kernel/time/tick-sched.c
> @@ -589,6 +589,32 @@ static enum hrtimer_restart tick_sched_timer(struct
> hrtimer *timer)
> return HRTIMER_RESTART;
> }
>
> +#if defined(CONFIG_X86) && defined(CONFIG_NO_HZ)
> +static __init int is_nohz_broken(void)
> +{
We definitely do not add x86 quirks into the generic code.
Is there really no other way to fix this problem ? Which chipset is
involved here ? SB400/600 perhaps ?
Thanks,
tglx
next prev parent reply other threads:[~2008-07-16 19:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 17:47 Thomas Renninger
2008-06-16 17:54 ` H. Peter Anvin
2008-06-16 20:06 ` Richard
2008-07-16 16:27 ` [PATCH] " Thomas Renninger
2008-07-16 19:03 ` Thomas Gleixner [this message]
2008-07-16 19:56 ` Thomas Renninger
2008-07-17 6:55 ` Richard
2008-07-17 10:51 ` Thomas Gleixner
2008-07-17 11:58 ` Richard
2008-07-17 11:11 ` Thomas Gleixner
2008-07-17 12:23 ` Richard
2008-07-17 12:03 ` Thomas Gleixner
2008-07-17 17:47 ` Richard
2008-07-17 16:59 ` Thomas Gleixner
2008-07-18 11:03 ` Richard
2008-07-18 17:12 ` Richard
2008-07-18 17:14 ` Richard
2008-07-18 17:15 ` Richard
2008-07-17 10:32 ` Thomas Renninger
2008-07-17 11:44 ` Richard
2008-07-17 11:05 ` Thomas Gleixner
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=alpine.LFD.1.10.0807162100380.4316@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=andreas.herrmann3@amd.com \
--cc=eumaster@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=trenn@suse.de \
--cc=tuxbox.guru@gmail.com \
--cc=uli.geins@geins-web.de \
/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®