| 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
| ||
|
Message-ID: <20071113215056.GB17593@one.firstfloor.org> Date: Tue, 13 Nov 2007 22:50:56 +0100 From: Andi Kleen <andi@...stfloor.org> To: Stephane Eranian <eranian@....hp.com> Cc: Andi Kleen <andi@...stfloor.org>, akpm@...l.org, Robert Richter <robert.richter@....com>, gregkh@...e.de, linux-kernel@...r.kernel.org, perfmon@...ali.hpl.hp.com, William Cohen <wcohen@...hat.com>, perfmon2-devel@...ts.sourceforge.net Subject: Re: [perfmon] Re: [perfmon2] perfmon2 merge news > Yes, horribly more complicated because of locking issues within perfmon. > As soon as you expose a file descriptor, you need some locking to prevent > multiple user threads (malicious or not) to compete to access the PMU state. Why do you need the file descriptor? One of the main problems with perfmon is the complicated user interface. Naively I would assume just some thread global state should be sufficient. > I think the value add of NMI can be as well achieved with advanced PMU features > such as Intel Core 2 PEBS. True probably, although only on CPUs that support PEBS. Dropping features for old CPUs is unfortunately quite difficult in Linux, and in this case probably not an option because there are so many of them (e.g. all of AMD not Fam10h) -Andi - 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