[PATCH 4/6] Fix HW breakpoint handlers
in [Kernel]
|
Prev: iommu-api: Add iommu_map and iommu_unmap functions
Next: [PATCH 1/6] Move poll into perf_event and allow for wakeups when fd has not been mmap'd. This is useful when using read() to read out the current counter value.
From: highguy on 7 Feb 2010 06:40 From: Stijn Devriendt <HIGHGuY(a)gmail.com> --- arch/x86/include/asm/hw_breakpoint.h | 2 +- arch/x86/kernel/hw_breakpoint.c | 2 +- kernel/hw_breakpoint.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/x86/include/asm/hw_breakpoint.h b/arch/x86/include/asm/hw_breakpoint.h index 0675a7c..d060a5c 100644 --- a/arch/x86/include/asm/hw_breakpoint.h +++ b/arch/x86/include/asm/hw_breakpoint.h @@ -54,7 +54,7 @@ extern int hw_breakpoint_exceptions_notify(struct notifier_block *unused, int arch_install_hw_breakpoint(struct perf_event *bp); void arch_uninstall_hw_breakpoint(struct perf_event *bp); -void hw_breakpoint_pmu_read(struct perf_event *bp); +void hw_breakpoint_pmu_update(struct perf_event *bp); void hw_breakpoint_pmu_unthrottle(struct perf_event *bp); extern void diff --git a/arch/x86/kernel/hw_breakpoint.c b/arch/x86/kernel/hw_breakpoint.c index 05d5fec..55469e0 100644 --- a/arch/x86/kernel/hw_breakpoint.c +++ b/arch/x86/kernel/hw_breakpoint.c @@ -543,7 +543,7 @@ int __kprobes hw_breakpoint_exceptions_notify( return hw_breakpoint_handler(data); } -void hw_breakpoint_pmu_read(struct perf_event *bp) +void hw_breakpoint_pmu_update(struct perf_event *bp) { /* TODO */ } diff --git a/kernel/hw_breakpoint.c b/kernel/hw_breakpoint.c index dbcbf6a..16b3a9b 100644 --- a/kernel/hw_breakpoint.c +++ b/kernel/hw_breakpoint.c @@ -448,6 +448,6 @@ core_initcall(init_hw_breakpoint); struct pmu perf_ops_bp = { .enable = arch_install_hw_breakpoint, .disable = arch_uninstall_hw_breakpoint, - .read = hw_breakpoint_pmu_read, + .update = hw_breakpoint_pmu_update, .unthrottle = hw_breakpoint_pmu_unthrottle }; -- 1.6.6 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |