linux-kernel - Re: [RFC PATCH 0/5] x86_64: enable clockevents and dynticks

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]

Message-Id: <1175549504.28263.184.camel@localhost.localdomain>
Date:	Mon, 02 Apr 2007 23:31:44 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Chris Wright <chrisw@...s-sol.org>
Cc:	Ingo Molnar <mingo@...e.hu>, john stultz <johnstul@...ibm.com>,
	Andi Kleen <ak@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/5] x86_64: enable clockevents and dynticks

On Sun, 2007-04-01 at 11:54 -0700, Chris Wright wrote:
> * Thomas Gleixner (tglx@...utronix.de) wrote:
> > On Sat, 2007-03-31 at 01:31 -0700, Chris Wright wrote:
> > > This series converts x86_64 timers to clockevents drivers
> > > and then enables dynticks.  There's some minor cleanups along
> > > the way.  The lapic broadcast mechanism is untested, I'm sure it
> > > still needs work, there's still some cruft in lapic_setup_timer.
> > > 
> > > This is just for comments at this point, now that it's working
> > > on my test box in both NO_HZ=n and NO_HZ=n configurations (typically
> > > using hpet).
> > 
> > Have you checked, if we could share the code between i386 and x86_64 at
> > least for PIT and HPET. I'm not sure about the local APIC, but I think
> > it might be doable as well.
> 
> Yes, that's part of why I did some of the cleanups that way, so that we
> could merge the two together later.

I'd prefer to get this done now. If we plug it in as is, the "merge
later" probably will never happen.

	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/