From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Don Zickus <dzickus@redhat.com>,
Stephane Eranian <eranian@google.com>,
Lin Ming <ming.m.lin@intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip, final] perf, x86: Add hw_watchdog_set_attr() in a sake of nmi-watchdog on P4
Date: Tue, 5 Jul 2011 19:25:16 +0400 [thread overview]
Message-ID: <20110705152515.GE4060@sun> (raw)
In-Reply-To: <20110705145656.GA18116@elte.hu>
On Tue, Jul 05, 2011 at 04:56:56PM +0200, Ingo Molnar wrote:
>
> * Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
>
> > On Tue, 2011-07-05 at 15:31 +0200, Ingo Molnar wrote:
> > > So there's lots of options to fix/improve this more intelligently.
> >
> > Sure, and I like the alternative encoding thing best, but doing
> > that will take time, in the meantime this patch, which is
> > relatively small (and easy to revert once we get something better
> > going) does fix a problem for those few unfortunate souls still
> > using P4 hardware.
>
> Well, the BUS_CYCLES thing looks similarly straightforward and should
> result in an even simpler patch.
>
nope, bus cycles count fsb driving which is not the same as execution unit
productions, so I fear it is not that reliable and i guess (note _guess_ here
since I can't prove it without hardware handy :) if cpus are stuck with endless
loop inside kernel we might miss such lockup (hard scenario, since there
will be activity on fsb anyway, but still).
> On P4 BUS_CYCLES would be able to co-exist with CPU_CYCLES so it will
> solve the P4 issue naturally as well.
>
> Thanks,
>
> Ingo
i don't think it changes much, Ingo, if I change it to bus cycles I still
will have to setup nmi-watchdog event separately (but simply with bus
event).
so an only option is the aliases, i'll try to deal with it but no milestones
Cyrill
next prev parent reply other threads:[~2011-07-05 15:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 10:03 [PATCH -tip, final] perf, x86: Add hw_watchdog_set_attr() in a sake of nmi-watchdog on P4 Cyrill Gorcunov
2011-07-05 10:20 ` Ingo Molnar
2011-07-05 10:34 ` Cyrill Gorcunov
2011-07-05 10:59 ` Ingo Molnar
2011-07-05 11:05 ` Cyrill Gorcunov
2011-07-05 11:20 ` Ingo Molnar
2011-07-05 11:36 ` Cyrill Gorcunov
2011-07-05 11:44 ` Ingo Molnar
2011-07-05 11:49 ` Cyrill Gorcunov
2011-07-05 12:14 ` Cyrill Gorcunov
2011-07-05 13:10 ` Ingo Molnar
2011-07-05 13:17 ` Peter Zijlstra
2011-07-05 13:31 ` Ingo Molnar
2011-07-05 14:19 ` Cyrill Gorcunov
2011-07-08 12:44 ` Ingo Molnar
2011-07-05 14:20 ` Peter Zijlstra
2011-07-05 14:40 ` Peter Zijlstra
2011-07-05 14:56 ` Ingo Molnar
2011-07-05 15:25 ` Cyrill Gorcunov [this message]
2011-07-06 7:01 ` Cyrill Gorcunov
2011-07-08 12:49 ` Ingo Molnar
2011-07-08 13:01 ` Cyrill Gorcunov
2011-07-08 13:09 ` Ingo Molnar
2011-07-08 13:12 ` Cyrill Gorcunov
2011-07-05 13:26 ` Cyrill Gorcunov
2011-07-05 12:24 ` Don Zickus
2011-07-05 12:26 ` Cyrill Gorcunov
2011-07-05 12:44 ` Don Zickus
2011-07-05 12:56 ` Cyrill Gorcunov
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=20110705152515.GE4060@sun \
--to=gorcunov@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox