From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Don Zickus <dzickus@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, Lin Ming <ming.m.lin@intel.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] perf, x86: P4 PMU - Add missing read of a counter before test
Date: Thu, 24 Mar 2011 21:26:12 +0300 [thread overview]
Message-ID: <4D8B8CC4.8000500@gmail.com> (raw)
In-Reply-To: <20110324182221.GF1239@redhat.com>
On 03/24/2011 09:22 PM, Don Zickus wrote:
> On Thu, Mar 24, 2011 at 07:46:40PM +0300, Cyrill Gorcunov wrote:
>>>> The read of a proper MSR register was missed so instead of a counter the
>>>> configration register is tested (it has ARCH_P4_UNFLAGGED_BIT always cleared)
>>>> and unflagged overflows never have been catched. Fix it by reading a proper
>>>> MSR register.
>>>
>>> So what effect does this have on the regular perf user? Please try to describe
>>> the real-life effect of the bug/problem fixed here.
>>>
>>> Thanks,
>>>
>>> Ingo
>>
>> Unflagged overflows never have been catched due to missed read of a register which
>> is to signalize about it, and as result unknown nmi may happen leading to
>> "Dazen and confused" message. That is what supposed to be in changelog?
>
> I think Ingo is looking for something like this:
>
Thanks Don, if Ingo agree I can update it.
--
Cyrill
next prev parent reply other threads:[~2011-03-24 18:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 8:29 [PATCH -tip] perf, x86: P4 PMU - Add missing read of a counter before test Cyrill Gorcunov
2011-03-24 8:48 ` Ingo Molnar
2011-03-24 9:33 ` Cyrill Gorcunov
2011-03-24 15:38 ` Cyrill Gorcunov
2011-03-24 16:33 ` Ingo Molnar
2011-03-24 16:46 ` Cyrill Gorcunov
2011-03-24 16:47 ` Cyrill Gorcunov
2011-03-24 16:51 ` Ingo Molnar
2011-03-24 17:06 ` Cyrill Gorcunov
2011-03-24 18:22 ` Don Zickus
2011-03-24 18:26 ` Cyrill Gorcunov [this message]
2011-03-24 20:03 ` Ingo Molnar
2011-03-24 12:28 ` Don Zickus
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=4D8B8CC4.8000500@gmail.com \
--to=gorcunov@gmail.com \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
/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.