linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Jiri Olsa <jolsa@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Namhyung Kim <namhyung@kernel.org>,
	linux-perf-users@vger.kernel.org
Subject: Re: [GIT PULL] Performance events changes for v6.12
Date: Thu, 19 Sep 2024 10:42:54 +0200	[thread overview]
Message-ID: <ZuvkDlws6xvijIuc@gmail.com> (raw)
In-Reply-To: <CAADWXX_mJr=hDkOWne831Fcm+wRxRnh9VvD2AMJJ5fStodyAgw@mail.gmail.com>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Wed, Sep 18, 2024 at 2:45 PM Ingo Molnar <mingo@kernel.org> wrote:
> >
> >  arch/x86/events/core.c                                |  63 +++++++++++++++++++
> >  arch/x86/events/intel/bts.c                           |   3 -
> [...]
> >  kernel/events/core.c                                  | 586 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------
> >  kernel/events/uprobes.c                               | 505 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------------------------------------------------
> 
> You seem to be cutting-and-pasting your diffstats from a *very* wide
> terminal window, resulting in a very messy diffstat result.

Yeah, sorry about that - it was a one-off manual diffstat due to the merge 
order between perf/urgent and perf/core, and indeed my terminal is ~240 
characters wide and I didn't notice the diffstat width-scaling weirdness.

> Please either pipe the git request-pull output to some tool (I suggest 
> just piping to 'xsel' or similar that does the 'cut' part for you, but 
> anything works - you can just do "| cat" to make the stdout not be the 
> terminal).
> 
> Or just use "--stat=80" to set the output width to a fixed sane thing, 
> instead of that insane 250+ character window width that it seems you are 
> using and that causes those overlong diffstat lines and makes it all hard 
> to read.

Will do next time it happens. Below is a belated diffstat with the correct 
width.

Thanks,

	Ingo

 arch/x86/events/core.c                             |  63 +++
 arch/x86/events/intel/bts.c                        |   3 -
 arch/x86/events/intel/cstate.c                     | 142 +----
 arch/x86/events/intel/pt.c                         |  29 +-
 arch/x86/events/intel/uncore.c                     |   9 +
 arch/x86/events/intel/uncore.h                     |   2 +
 arch/x86/events/intel/uncore_snb.c                 | 185 ++++++-
 drivers/dma/idxd/idxd.h                            |   7 -
 drivers/dma/idxd/init.c                            |   3 -
 drivers/dma/idxd/perfmon.c                         |  98 +---
 drivers/iommu/intel/iommu.h                        |   2 -
 drivers/iommu/intel/perfmon.c                      | 111 +---
 include/linux/cpuhotplug.h                         |   2 -
 include/linux/perf_event.h                         |  32 +-
 include/linux/rbtree.h                             |  67 +++
 include/linux/uprobes.h                            |  48 +-
 kernel/events/core.c                               | 586 +++++++++++++++------
 kernel/events/uprobes.c                            | 505 ++++++++++--------
 kernel/trace/bpf_trace.c                           |  38 +-
 kernel/trace/trace_uprobe.c                        |  44 +-
 .../selftests/bpf/bpf_testmod/bpf_testmod.c        |  27 +-
 21 files changed, 1146 insertions(+), 857 deletions(-)

  reply	other threads:[~2024-09-19  8:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18 12:45 [GIT PULL] Performance events changes for v6.12 Ingo Molnar
2024-09-18 13:00 ` Linus Torvalds
     [not found]   ` <ZuvhwjNgDmpmReUl@gmail.com>
2024-09-19  8:42     ` Linus Torvalds
2024-09-19  8:48       ` Ingo Molnar
2024-09-19  8:50         ` Linus Torvalds
2024-09-18 13:12 ` Linus Torvalds
2024-09-19  8:42   ` Ingo Molnar [this message]
2024-09-18 14:00 ` pr-tracker-bot
2024-09-18 22:26 ` Stephen Rothwell
2024-09-19  9:53   ` Ingo Molnar
2024-09-19 10:42     ` Stephen Rothwell
2024-09-21 22:39     ` Linus Torvalds
2024-09-22 19:50       ` Linus Torvalds
2024-09-23 15:27         ` Ingo Molnar

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=ZuvkDlws6xvijIuc@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@redhat.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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).