All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <m.chehab@samsung.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Chen, Gong" <gong.chen@linux.intel.com>,
	tony.luck@intel.com, arozansk@redhat.com,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH 1/2] trace, RAS: Add basic RAS trace event
Date: Thu, 06 Mar 2014 08:43:20 -0300	[thread overview]
Message-ID: <20140306084320.539ec76e@samsung.com> (raw)
In-Reply-To: <20140306111852.GA24629@pd.tnic>

Em Thu, 06 Mar 2014 12:18:52 +0100
Borislav Petkov <bp@alien8.de> escreveu:

> On Tue, Mar 04, 2014 at 04:23:16AM -0500, Chen, Gong wrote:
> > To avoid the confuision of usage for RAS related trace event, add
> > an unified RAS trace event stub.
> > 
> > Signed-off-by: Chen, Gong <gong.chen@linux.intel.com>
> > ---
> >  drivers/edac/edac_mc.c    |  3 ---
> >  kernel/trace/Makefile     |  1 +
> >  kernel/trace/ras-traces.c | 12 ++++++++++++
> >  3 files changed, 13 insertions(+), 3 deletions(-)
> >  create mode 100644 kernel/trace/ras-traces.c
> > 
> > diff --git a/drivers/edac/edac_mc.c b/drivers/edac/edac_mc.c
> > index 33edd67..28c1695 100644
> > --- a/drivers/edac/edac_mc.c
> > +++ b/drivers/edac/edac_mc.c
> > @@ -33,9 +33,6 @@
> >  #include <asm/edac.h>
> >  #include "edac_core.h"
> >  #include "edac_module.h"
> > -
> > -#define CREATE_TRACE_POINTS
> > -#define TRACE_INCLUDE_PATH ../../include/ras
> >  #include <ras/ras_event.h>
> >  
> >  /* lock to memory controller's control array */
> > diff --git a/kernel/trace/Makefile b/kernel/trace/Makefile
> > index 1378e84..167193a 100644
> > --- a/kernel/trace/Makefile
> > +++ b/kernel/trace/Makefile
> > @@ -52,6 +52,7 @@ endif
> >  obj-$(CONFIG_EVENT_TRACING) += trace_events_filter.o
> >  obj-$(CONFIG_EVENT_TRACING) += trace_events_trigger.o
> >  obj-$(CONFIG_KPROBE_EVENT) += trace_kprobe.o
> > +obj-$(CONFIG_TRACEPOINTS) += ras-traces.o
> 
> Actually I was thinking of slowly concentrating all the RAS stuff into
> arch/x86/ras/.
> 
> Just add arch/x86/ras/trace.c instead please.

I would prefer to keep this out of arch/, because there are some 
parts of the ras infra that aren't x86 specific.

So, it would be better to put those at /drivers/ras, and add a
"depends on X86" for the x86 specifics.

Going further, it also make sense to move the EDAC drivers into it.

Regards,
Mauro

  reply	other threads:[~2014-03-06 11:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  9:23 trace, RAS: New eMCA trace event interface Chen, Gong
2014-03-04  9:23 ` [PATCH 1/2] trace, RAS: Add basic RAS trace event Chen, Gong
2014-03-06 11:18   ` Borislav Petkov
2014-03-06 11:43     ` Mauro Carvalho Chehab [this message]
2014-03-06 12:17       ` Borislav Petkov
2014-03-06 13:06         ` Mauro Carvalho Chehab
2014-03-06 15:26           ` Borislav Petkov
2014-03-06 15:39             ` Mauro Carvalho Chehab
2014-03-07  6:21               ` Chen, Gong
2014-03-07  9:08                 ` Mauro Carvalho Chehab
2014-03-04  9:23 ` [PATCH 2/2] trace, RAS: Add eMCA trace event interface Chen, Gong
2014-03-07 11:44   ` Borislav Petkov
2014-03-10  8:22     ` Chen, Gong
2014-03-10 10:04       ` Mauro Carvalho Chehab
2014-03-10 10:31         ` Borislav Petkov
2014-03-10 11:41           ` Mauro Carvalho Chehab
2014-03-10 13:29             ` Borislav Petkov
2014-03-10 17:37               ` Luck, Tony
2014-03-11 14:27                 ` Borislav Petkov
2014-03-10 10:33       ` Borislav Petkov
2014-03-10 17:42       ` Luck, Tony
2014-03-11  7:03         ` Chen, Gong
2014-03-04 17:54 ` trace, RAS: New " Luck, Tony
2014-03-07  9:10   ` Mauro Carvalho Chehab
2014-03-10 18:55     ` Tony Luck
2014-03-10 19:41       ` Mauro Carvalho Chehab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140306084320.539ec76e@samsung.com \
    --to=m.chehab@samsung.com \
    --cc=arozansk@redhat.com \
    --cc=bp@alien8.de \
    --cc=gong.chen@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=tony.luck@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.