All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: jolsa@kernel.org, adrian.hunter@intel.com,
	linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH v1 03/10] tools, perf, script: Add --insn-trace for instruction decoding
Date: Wed, 19 Sep 2018 17:38:40 -0300	[thread overview]
Message-ID: <20180919203840.GL31812@kernel.org> (raw)
In-Reply-To: <20180919200202.lzopwvlgdnsrokyh@two.firstfloor.org>

Em Wed, Sep 19, 2018 at 01:02:04PM -0700, Andi Kleen escreveu:
> On Wed, Sep 19, 2018 at 03:12:47PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Aug 29, 2018 at 10:18:27AM -0700, Andi Kleen escreveu:
> > > From: Andi Kleen <ak@linux.intel.com>
> > > 
> > > Add a --insn-trace short hand option for decoding and disassembling
> > > instruction streams for intel_pt. This automatically pipes the
> > > output into the xed disassembler to generate disassembled instructions.
> > > This just makes this use model much nicer to use
> > 
> > Would be nice to provide at least an URL to where to find xed, I tried
> > this:
> > 
> > [root@seventh ~]# dnf search xed
> > Last metadata expiration check: 0:25:39 ago on Wed 19 Sep 2018 02:42:36 PM -03.
> > =================================================================================== Name Exactly Matched: xed ====================================================================================
> > xed.i686 : X-Apps [Text] Editor (Cross-DE, backward-compatible, GTK3, traditional UI)
> > xed.x86_64 : X-Apps [Text] Editor (Cross-DE, backward-compatible, GTK3, traditional UI)
> > 
> > https://github.com/intelxed
> > 
> > So I have to install a build system and then install it to then build
> > intelxed?
> 
> Yes that's right.

Sure, so please add this extra info you provided here there, please, to
help speed up testing of your work.

I think this should go in the documentation section as well.
 
> I think some distros have it already packaged.
 
> 
> git clone https://github.com/intelxed/mbuild.git mbuild
> git clone https://github.com/intelxed/xed
> cd xed
> mkdir obj
> cd obj
> ../mfile.py
> sudo ../mfile.py --prefix=/usr/local install
> 
> -Andi

  reply	other threads:[~2018-09-19 20:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 17:18 Make perf script easier to use for itrace Andi Kleen
2018-08-29 17:18 ` [PATCH v1 01/10] perf tools: Report itrace options in help Andi Kleen
2018-08-30  8:56   ` Jiri Olsa
2018-08-29 17:18 ` [PATCH v1 02/10] tools, pager: Support overwriting the pager Andi Kleen
2018-08-29 17:18 ` [PATCH v1 03/10] tools, perf, script: Add --insn-trace for instruction decoding Andi Kleen
2018-08-30  8:56   ` Jiri Olsa
2018-08-30 13:55     ` Andi Kleen
2018-09-19 18:12   ` Arnaldo Carvalho de Melo
2018-09-19 20:02     ` Andi Kleen
2018-09-19 20:38       ` Arnaldo Carvalho de Melo [this message]
2018-08-29 17:18 ` [PATCH v1 04/10] perf, tools, script: Allow sym and dso without ip, addr Andi Kleen
2018-08-30  8:56   ` Jiri Olsa
2018-08-29 17:18 ` [PATCH v1 05/10] perf, tools, script: Print DSO for callindent Andi Kleen
2018-08-30  8:57   ` Jiri Olsa
2018-08-29 17:18 ` [PATCH v1 06/10] tools, perf, script: Set user_set/wildcard_set for +- fields in -F Andi Kleen
2018-08-30  8:59   ` Jiri Olsa
2018-08-29 17:18 ` [PATCH v1 07/10] perf, tools, script: Implement - for typed fields Andi Kleen
2018-08-29 17:18 ` [PATCH v1 08/10] perf, tools, script: Make itrace script default to all calls Andi Kleen
2018-08-29 17:18 ` [PATCH v1 09/10] tools, perf, script: Add --call-trace and --call-ret-trace Andi Kleen
2018-08-29 17:18 ` [PATCH v1 10/10] tools, perf, script: Implement --graph-function Andi Kleen
2018-08-30  8:42 ` Make perf script easier to use for itrace Jiri Olsa

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=20180919203840.GL31812@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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 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.