Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934572AbbGHKX2 (ORCPT ); Wed, 8 Jul 2015 06:23:28 -0400 Received: from mga11.intel.com ([192.55.52.93]:33559 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933020AbbGHKXY (ORCPT ); Wed, 8 Jul 2015 06:23:24 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,431,1432623600"; d="scan'208";a="520732343" From: Alexander Shishkin To: Chunyan Zhang , rostedt@goodmis.org, mingo@redhat.com Cc: mathieu.poirier@linaro.org, serge.broslavsky@linaro.org, broonie@kernel.org, zhang.lyra@gmail.com, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH v3 1/4] STM trace event: Adding generic buffer interface driver In-Reply-To: References: User-Agent: Notmuch/0.20.1 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Wed, 08 Jul 2015 13:23:21 +0300 Message-ID: <87zj37lzhi.fsf@ashishki-desk.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3231 Lines: 89 Chunyan Zhang writes: > From: Mathieu Poirier > > This patch adds a driver that models itself as an stm_source and > who's sole purpose is to export an interface to the rest of the > kernel. Once the stm and stm_source have been linked via sysfs, > everything that is passed to the interface will endup in the STM > trace engine. > > Signed-off-by: Mathieu Poirier > Signed-off-by: Chunyan Zhang > --- > drivers/stm/Kconfig | 11 +++++++++++ > drivers/stm/Makefile | 2 ++ > drivers/stm/stm_trace_event.c | 46 +++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 59 insertions(+) > create mode 100644 drivers/stm/stm_trace_event.c > > diff --git a/drivers/stm/Kconfig b/drivers/stm/Kconfig > index 6f2db70..8ead418 100644 > --- a/drivers/stm/Kconfig > +++ b/drivers/stm/Kconfig > @@ -25,3 +25,14 @@ config STM_SOURCE_CONSOLE > > If you want to send kernel console messages over STM devices, > say Y. > + > +config STM_TRACE_EVENT > + tristate "Redirect/copy the output from kernel trace event to STM engine" > + depends on STM > + help > + This option can be used to redirect or copy the output from kernel trace > + event to STM engine. Enabling this option will introduce a slight > + timing effect. > + > + If you want to send kernel trace event messages over STM devices, > + say Y. > diff --git a/drivers/stm/Makefile b/drivers/stm/Makefile > index 74baf59..55b152c 100644 > --- a/drivers/stm/Makefile > +++ b/drivers/stm/Makefile > @@ -5,3 +5,5 @@ stm_core-y := core.o policy.o > obj-$(CONFIG_STM_DUMMY) += dummy_stm.o > > obj-$(CONFIG_STM_SOURCE_CONSOLE) += console.o > + > +obj-$(CONFIG_STM_TRACE_EVENT) += stm_trace_event.o > diff --git a/drivers/stm/stm_trace_event.c b/drivers/stm/stm_trace_event.c > new file mode 100644 > index 0000000..bc77dae > --- /dev/null > +++ b/drivers/stm/stm_trace_event.c > @@ -0,0 +1,46 @@ > +/* > + * Simple kernel driver to link kernel trace event and an STM device > + * Copyright (c) 2015, Linaro Ltd. > + * > + * This program is free software; you can redistribute it and/or modify it > + * under the terms and conditions of the GNU General Public License, > + * version 2, as published by the Free Software Foundation. > + * > + * This program is distributed in the hope it will be useful, but WITHOUT > + * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or > + * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for > + * more details. > + */ > + > +#include > +#include > +#include > +#include > +#include > + > +static struct stm_source_data stm_trace_event_data = { > + .name = "stm_trace_event", > + .nr_chans = 1, One question is: do we want to cram ftrace data from all cpus into one channel or use a channel per cpu? Regards, -- Alex -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/