From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stephane Eranian <eranian@google.com>,
linux-kernel@vger.kernel.org, peterz@infradead.org,
markus@trippelsdorf.de, paulus@samba.org
Subject: Re: [PATCH] perf: fix assertion failure in x86_pmu_start()
Date: Tue, 07 Feb 2012 11:25:22 +0100 [thread overview]
Message-ID: <1328610322.2232.1.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <20120207084156.GA15359@elte.hu>
Le mardi 07 février 2012 à 09:41 +0100, Ingo Molnar a écrit :
> Were these messages introduced by:
>
> e050e3f0a71b: perf: Fix broken interrupt rate throttling
>
> as well?
>
> In any case I'm holding off on applying the patch before this is
> resolved.
Reverting e050e3f0a71b solves all my problems, no more warnings.
$ perf record -a -g hackbench 10 thread 4000
Running with 10*40 (== 400) tasks.
Time: 13.181
[ perf record: Woken up 59 times to write data ]
[ perf record: Captured and wrote 16.874 MB perf.data (~737228 samples)
]
$ perf record -a -g hackbench 10 thread 4000
Running with 10*40 (== 400) tasks.
Time: 13.124
[ perf record: Woken up 61 times to write data ]
[ perf record: Captured and wrote 16.533 MB perf.data (~722349 samples)
]
next prev parent reply other threads:[~2012-02-07 10:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 20:53 Stephane Eranian
2012-02-07 8:34 ` Eric Dumazet
2012-02-07 8:41 ` Ingo Molnar
2012-02-07 8:55 ` Eric Dumazet
2012-02-07 10:25 ` Eric Dumazet [this message]
2012-02-07 10:31 ` Stephane Eranian
2012-02-07 10:36 ` Eric Dumazet
2012-02-07 10:40 ` Stephane Eranian
2012-02-07 11:24 ` Eric Dumazet
2012-02-07 11:27 ` Stephane Eranian
2012-02-07 11:36 ` Ingo Molnar
2012-02-07 10:49 ` Ingo Molnar
2012-02-07 11:07 ` Stephane Eranian
2012-02-07 9:17 ` Stephane Eranian
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=1328610322.2232.1.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
--to=eric.dumazet@gmail.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@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
all inboxes | Powered by JetHome®