linux-kernel - Re: [GIT PULL] oprofile fixes for v2.6.40

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20110530101619.GC20052@erda.amd.com>
Date:	Mon, 30 May 2011 12:16:19 +0200
From:	Robert Richter <robert.richter@....com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"oprofile-list@...ts.sourceforge.net" 
	<oprofile-list@...ts.sourceforge.net>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [GIT PULL] oprofile fixes for v2.6.40

On 30.05.11 06:09:56, Ingo Molnar wrote:
> 
> * Robert Richter <robert.richter@....com> wrote:
> 
> > > But i really do not see how this can work. get_eilvt() twiddles 
> > > the APIC LVT of this current CPU. Does IBS only activate on a 
> > > single CPU? How will this LVT entry be cleared on deinit?
> > 
> > This is done on the current cpu to get the offset which is then 
> > used on all cpus of the system. The actually per-core setup for ibs 
> > is in op_amd_setup_ctrs(). Deinit is in op_amd_cpu_shutdown().
> 
> The way IBS is set up is not very obvious and atypical of existing 
> preempt_*() patters. Might be worth adding a comment to the 
> preempt_disable(), to unconfuse unsuspecting readers who are 
> wondering about its oddness?

Yes, will add some comments.

> Anyway, i suspected that it was correctly working code so i pulled it 
> and pushed it to Linus, it should all be in 3.0-rc1.

Have seen it, thanks Ingo,

-Robert

-- 
Advanced Micro Devices, Inc.
Operating System Research Center

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