linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rostedt@goodmis.org (Steven Rostedt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 5/5] arm64: Trace emulation of AArch32 legacy instructions
Date: Wed, 5 Nov 2014 10:05:11 -0500	[thread overview]
Message-ID: <20141105100511.2daef605@gandalf.local.home> (raw)
In-Reply-To: <20141105144619.GI32700@e104818-lin.cambridge.arm.com>

On Wed, 5 Nov 2014 14:46:19 +0000
Catalin Marinas <catalin.marinas@arm.com> wrote:

> On Mon, Oct 27, 2014 at 06:40:07PM +0000, Punit Agrawal wrote:
> > Introduce an event to trace the usage of emulated instructions. The
> > trace event is intended to help identify and encourage the migration
> > of legacy software using the emulation features.
> > 
> > Use this event to trace usage of swp and CP15 barrier emulation.
> > 
> > Cc: Steven Rostedt <rostedt@goodmis.org>
> > Signed-off-by: Punit Agrawal <punit.agrawal@arm.com>
> > ---
> >  arch/arm64/kernel/Makefile                 |  1 +
> >  arch/arm64/kernel/armv8_deprecated.c       | 19 ++++++++++++--
> >  arch/arm64/kernel/trace-events-emulation.h | 40 ++++++++++++++++++++++++++++++
> >  3 files changed, 58 insertions(+), 2 deletions(-)
> >  create mode 100644 arch/arm64/kernel/trace-events-emulation.h
> > 
> > diff --git a/arch/arm64/kernel/Makefile b/arch/arm64/kernel/Makefile
> > index 5362578..1fc7abd 100644
> > --- a/arch/arm64/kernel/Makefile
> > +++ b/arch/arm64/kernel/Makefile
> > @@ -5,6 +5,7 @@
> >  CPPFLAGS_vmlinux.lds	:= -DTEXT_OFFSET=$(TEXT_OFFSET)
> >  AFLAGS_head.o		:= -DTEXT_OFFSET=$(TEXT_OFFSET)
> >  CFLAGS_efi-stub.o 	:= -DTEXT_OFFSET=$(TEXT_OFFSET)
> > +CFLAGS_armv8_deprecated.o := -I$(src)
> 
> Why do you need this?

It has to do with the TRACE_EVENT magic.

Read samples/trace_events/Makefile

> 
> >  CFLAGS_REMOVE_ftrace.o = -pg
> >  CFLAGS_REMOVE_insn.o = -pg
> > diff --git a/arch/arm64/kernel/armv8_deprecated.c b/arch/arm64/kernel/armv8_deprecated.c
> > index fded15f..d376fe2 100644
> > --- a/arch/arm64/kernel/armv8_deprecated.c
> > +++ b/arch/arm64/kernel/armv8_deprecated.c
> > @@ -15,6 +15,9 @@
> >  #include <linux/slab.h>
> >  #include <linux/sysctl.h>
> >  
> > +#define CREATE_TRACE_POINTS
> > +#include "trace-events-emulation.h"
> 
> Using double quotes should be fine for the current directory.
> 

No it is not enough. It not only gets included by this file, but also
gets included by include/trace/ftrace.h with:

#include TRACE_INCLUDE(TRACE_INCLUDE_FILE)

Without that -I$(src) added, this include will fail.

-- Steve

  reply	other threads:[~2014-11-05 15:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 18:40 [PATCHv3 0/5] Legacy instruction emulation for arm64 Punit Agrawal
2014-10-27 18:40 ` [PATCHv3 1/5] arm64: Add support for hooks to handle undefined instructions Punit Agrawal
2014-11-05 11:27   ` Catalin Marinas
2014-11-06 12:20     ` Punit Agrawal
2014-10-27 18:40 ` Punit Agrawal
2014-10-29 14:26   ` Punit Agrawal
2014-10-27 18:40 ` [PATCHv3 2/5] arm64: Add AArch32 instruction set condition code checks Punit Agrawal
2014-10-29 15:21   ` Russell King - ARM Linux
2014-10-29 16:54     ` Punit Agrawal
2014-11-05 16:14     ` Catalin Marinas
2014-11-05 16:19       ` Will Deacon
2014-11-05 11:28   ` Catalin Marinas
2014-10-27 18:40 ` [PATCHv3 3/5] arm64: Port SWP/SWPB emulation support from arm Punit Agrawal
2014-11-05 11:47   ` Catalin Marinas
2014-11-07 18:15     ` Punit Agrawal
2014-10-27 18:40 ` [PATCHv3 4/5] arm64: Emulate CP15 Barrier instructions Punit Agrawal
2014-11-05 13:05   ` Catalin Marinas
2014-11-07 16:07     ` Punit Agrawal
2014-11-13 10:34       ` Catalin Marinas
2014-11-05 14:51   ` Catalin Marinas
2014-11-07 13:03     ` Punit Agrawal
2014-10-27 18:40 ` [PATCHv3 5/5] arm64: Trace emulation of AArch32 legacy instructions Punit Agrawal
2014-11-05 14:46   ` Catalin Marinas
2014-11-05 15:05     ` Steven Rostedt [this message]
2014-11-05 15:52       ` Catalin Marinas
2014-11-10 18:27   ` Will Deacon
2014-11-12 11:31     ` Punit Agrawal

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=20141105100511.2daef605@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).