linux-kernel - [PATCH 0/4] perf, x86: collection of pentium 4 fixes

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: <1303398203-2918-1-git-send-email-dzickus@redhat.com>
Date:	Thu, 21 Apr 2011 11:03:19 -0400
From:	Don Zickus <dzickus@...hat.com>
To:	<x86@...nel.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Don Zickus <dzickus@...hat.com>
Subject: [PATCH 0/4] perf, x86: collection of pentium 4 fixes

This patch series has various clean ups for the P4 perf nmi layer.
Some of the changes touch the other platforms but those should be minimally
intrusive.

It would be nice to get these into 2.6.39 as two patches fix 'unknown' NMIs,
which is listed as a regression from 2.6.38.

Cyrill Gorcunov (3):
  perf, x86: P4 PMU -- Use perf_sample_data_init helper
  perf, x86: P4 PMU - Don't forget to clear cpuc->active_mask on
    overflow
  perf, x86: Add PERF_COUNT_HW_NMI_WATCHDOG event

Don Zickus (1):
  perf, nmi: Move LVT un-masking into irq handlers

 arch/x86/kernel/cpu/perf_event.c       |    5 ++-
 arch/x86/kernel/cpu/perf_event_amd.c   |    1 +
 arch/x86/kernel/cpu/perf_event_intel.c |    4 +++
 arch/x86/kernel/cpu/perf_event_p4.c    |   34 +++++++++++++++++++++++++------
 arch/x86/kernel/cpu/perf_event_p6.c    |    1 +
 include/linux/perf_event.h             |    1 +
 kernel/watchdog.c                      |    2 +-
 7 files changed, 38 insertions(+), 10 deletions(-)

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