linux-kernel - Re: [patch] high-res timers: UP resume fix

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:	Sat, 7 Apr 2007 11:48:42 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	tglx@...utronix.de
Cc:	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Soeren Sonnenburg <kernel@....de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Len Brown <len.brown@...el.com>
Subject: Re: [patch] high-res timers: UP resume fix

On Saturday, 7 April 2007 10:48, Thomas Gleixner wrote:
> On Sat, 2007-04-07 at 10:25 +0200, Ingo Molnar wrote:
> > * Ingo Molnar <mingo@...e.hu> wrote:
> > 
> > > [...] Soeren, can you confirm that you are using a !CONFIG_SMP kernel, 
> > > and if yes, does the patch below fix the resume problem for you?
> > 
> > hm, you seem to have a CONFIG_SMP=y kernel. I dont immediately see where 
> > we re-enable interrupts in the SMP case, but could you try my patch 
> > nevertheless
> 
> We do in on_each_cpu() unconditionally. I missed that.

BTW, the on_each_cpu() in clock_was_set() is unnecessary, because
timekeeping_resume() is always run on one CPU.

Greetings,
Rafael
-
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/