linux-kernel - Re: [PATCH] Re: AMD Mobile Semprons (3500+, 3600+,...) break with nohz and highres enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 16 Jul 2008 21:03:12 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Thomas Renninger <trenn@...e.de>
cc:	Ingo Molnar <mingo@...e.hu>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"andreas.herrmann3" <andreas.herrmann3@....com>,
	Richard <tuxbox.guru@...il.com>, eumaster@...il.com,
	uli.geins@...ns-web.de
Subject: Re: [PATCH] Re: AMD Mobile Semprons (3500+, 3600+,...) break with
 nohz and highres enabled

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/