Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752631AbcDOGyU (ORCPT ); Fri, 15 Apr 2016 02:54:20 -0400 Received: from mail-ig0-f176.google.com ([209.85.213.176]:36568 "EHLO mail-ig0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751791AbcDOGyT (ORCPT ); Fri, 15 Apr 2016 02:54:19 -0400 From: Howard Cochran To: linux-kernel@vger.kernel.org Cc: Steven Rostedt , Ingo Molnar , Howard Cochran Subject: [PATCHSET] tracing: Make event triggers affect correct instance Date: Fri, 15 Apr 2016 02:53:45 -0400 Message-Id: <1460703230-13307-1-git-send-email-hcochran@kernelspring.com> X-Mailer: git-send-email 1.9.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 931 Lines: 19 Although all of the trace event triggers can be used in instances, most of them affect the top-level instance even when triggered from within an instance. This patch set makes them affect the instance in which the trigger occurred. The enable_event & disable_event triggers already work within the correct instance, so these are unchanged. The same problem also exists with the function probe triggers, but they will be fixed in a later patch set. Patch 1 is preparatory. Patch 2 fixes the stacktrace event trigger Patch 3 fixes the traceon & traceoff event triggers Patch 4 fixes the snapshot event trigger Patch 5 Makes related warning messages also go to the correct instance kernel/trace/trace.c | 96 +++++++++++++++++++++++++------------ kernel/trace/trace.h | 14 +++++- kernel/trace/trace_events_trigger.c | 62 ++++++++++++++---------- 3 files changed, 113 insertions(+), 59 deletions(-)