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: Tue, 6 Dec 2011 10:29:05 +0100 From: Robert Richter <robert.richter@....com> To: Stephane Eranian <eranian@...gle.com> CC: Frederic Weisbecker <fweisbec@...il.com>, "acme@...hat.com" <acme@...stprotocols.net>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "peterz@...radead.org" <peterz@...radead.org>, "dsahern@...il.com" <dsahern@...il.com>, "ak@...ux.intel.com" <ak@...ux.intel.com>, "mingo@...e.hu" <mingo@...e.hu> Subject: Re: [PATCH] perf: make perf.data more self-descriptive (v8) On 05.12.11 11:24:05, Stephane Eranian wrote: > The one thing I realized last week, is that all that header information, incl. > the features bits do not seem to appear in the file perf.data file when you > use the perf record pipe mode. We need to fix that otherwise, if you > depend on information in those bits, it won't always be present. That's > a major issue. Yes, this is because pipes are not seakable, which is necessary to write the features. -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/
Powered by blists - more mailing lists