linux-kernel - [PATCH v1 0/5] perf: Untangle aux refcounting

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-next>] [day] [month] [year] [list]

Message-Id: <1449764194-26565-1-git-send-email-alexander.shishkin@linux.intel.com>
Date:	Thu, 10 Dec 2015 18:16:29 +0200
From:	Alexander Shishkin <alexander.shishkin@...ux.intel.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	vince@...ter.net, eranian@...gle.com,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Subject: [PATCH v1 0/5] perf: Untangle aux refcounting

Hi Peter,

Here's the full patchset. I rebased it on top of your queue, for the
event_function_call() and whatnots and dropped similar patches from
this set. Otherwise, the difference is in 2/5.

Alexander Shishkin (5):
  perf: Refuse to begin aux transaction after aux_mmap_count drops
  perf: Free aux pages in unmap path
  perf: Document aux api usage
  perf/x86/intel/pt: Move transaction start/stop to pmu start/stop
    callbacks
  perf/x86/intel/bts: Move transaction start/stop to start/stop
    callbacks

 arch/x86/kernel/cpu/perf_event_intel_bts.c | 105 +++++++++++++----------------
 arch/x86/kernel/cpu/perf_event_intel_pt.c  |  85 ++++++++---------------
 kernel/events/core.c                       |  87 +++++++++++++++++++++++-
 kernel/events/internal.h                   |   1 -
 kernel/events/ring_buffer.c                |  52 +++++++-------
 5 files changed, 187 insertions(+), 143 deletions(-)

-- 
2.6.2

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