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
| ||
|
Date: Thu, 12 Sep 2013 06:34:39 -0700 From: David Ahern <dsahern@...il.com> To: Ingo Molnar <mingo@...nel.org> CC: linux-kernel@...r.kernel.org, acme@...stprotocols.net, fweisbec@...il.com, peterz@...radead.org, jolsa@...hat.com, namhyung@...nel.org, xiaoguangrong@...ux.vnet.ibm.com, runzhen@...ux.vnet.ibm.com, Runzhen Wang <icycoder@...il.com> Subject: Re: [PATCH 14/16] perf kvm: reuse some code of perf_kvm__timerfd_create() On 9/12/13 6:08 AM, Ingo Molnar wrote: > > btw., I tried to build perf on a really old distro that has no timerfd.h, > and got: Right. I hit that last week or so with RHEL5 as a build server. timerfd was introduced before perf so any system with perf capability will also have timerfd. So the problem is strictly building perf on an older system. Are you using a tarball created by one of the 'make perf-*' options? Is the expectation that the resulting perf binary will be used for both record and report paths? I could compile out the feature if timerfd is not available or add a compat layer in perf (e.g., if not defined, define it). David -- 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