mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Tejun Heo <tj@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [Bug] ARM 'perf' regression by commit a43cb95d5
Date: Fri, 17 May 2013 10:54:23 +0100	[thread overview]
Message-ID: <20130517095423.GD23112@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CACVXFVP56EJb0BZ+w6hVAukQ-mN0e0Jn_GLw3XqXQqMwVGfNdA@mail.gmail.com>

On Fri, May 17, 2013 at 10:48:23AM +0100, Ming Lei wrote:
> On Fri, May 17, 2013 at 5:36 PM, Will Deacon <will.deacon@arm.com> wrote:
> >
> > It's probably easier if you choose a workload, otherwise it's difficult to
> > see what is `correct' and what is broken. For example, your broken output
> > seems to be in the smsc95xx driver, so assumedly there's a bunch of
> > networking going on whereas your other output is in cpuidle_enter_state.
> 
> If all modules are removed, the result will become OK. And if I only insert one
> module, the top sample will fall inside the only module, but I am sure
> nothing is working on the symbols of the module.

Can you check your dmesg please? I suppose the smsc95xx driver might be
screaming about something and somehow the changes to the reg printing have
made it get stuck.

> >
> > We need an apples-for-apples comparison if you think there's a bug in the
> > kernel. Can you try profiling hackbench or something?
> >
> >> Or could anyone else try to verify the problem on their own environment?
> >
> > How are you running perf top?
> 
> sudo perf top

... and did hackbench make any difference (i.e. is the profile more stable)?

Will

  reply	other threads:[~2013-05-17  9:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17  2:16 Ming Lei
2013-05-17  2:28 ` Ming Lei
2013-05-17  8:55 ` Will Deacon
2013-05-17  9:27   ` Ming Lei
2013-05-17  9:36     ` Will Deacon
2013-05-17  9:48       ` Ming Lei
2013-05-17  9:54         ` Will Deacon [this message]
2013-05-17 10:07           ` Ming Lei
2013-05-17 15:59             ` Will Deacon
2013-05-28 10:18               ` Ming Lei

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=20130517095423.GD23112@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=ming.lei@canonical.com \
    --cc=tj@kernel.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

all inboxes | Powered by JetHome®