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, 7 Feb 2007 00:28:28 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Daniel Walker <dwalker@...sta.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.20-rc6-mm3


* Daniel Walker <dwalker@...sta.com> wrote:

> On Wed, 2007-02-07 at 00:14 +0100, Ingo Molnar wrote:
> > * Daniel Walker <dwalker@...sta.com> wrote:
> > 
> > > On Tue, 2007-02-06 at 23:56 +0100, Ingo Molnar wrote:
> > > 
> > > > changing the current 'timer' entry (which is line 2 of /proc/interrupts) 
> > > > to be 'listed as lapic-timer' and to 'replace it with the count from 
> > > > LOC' is faking a count in a line where nothing like that should be.
> > > 
> > > This point is getting irrelevant ..
> > 
> > it is very much relevant: faking a count is something we /dont/ want 
> > to do with /proc/interrupts, for (very) basic compatibility, 
> > simplicity and policy reasons. And that is precisely what your 
> > suggestion was to 'solve' this supposed 'problem' - so it's very 
> > much relevant.
> 
> As I said you are misunderstanding me .. which is why this is not 
> relevant any more ..

actually, i quoted what you said:

| If we change the current "timer" entry to be listed as "lapic-timer" 
| and not "IO-APIC-edge" (or one of the other names) and replace it with 
| the count from LOC

this is a pretty clear sentence, i dont think i misunderstood anything 
about it. If i did, please point it out specifically.

	Ingo
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ