From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jeroen Van den Keybus <jeroen.vandenkeybus@gmail.com>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] SMI count polling
Date: Mon, 14 Sep 2015 09:45:27 +0200 [thread overview]
Message-ID: <20150914074527.GA17701@hermes.click-hack.org> (raw)
In-Reply-To: <CAPRPZsB5PCNmrrqfE4u8E23JEL=_aRhTPS=kUHtEZwpRPjhagw@mail.gmail.com>
On Mon, Sep 14, 2015 at 09:41:47AM +0200, Jeroen Van den Keybus wrote:
> Gilles,
>
>
> > Would it make sense to
> > poll that MSR in the I-pipe tracer for the processors which support
> > it? Or is it really not generic enough?
>
> We have been using the SMI count in the past to trace the origin of
> unexpected delays. I'd say the support for this count would be very
> useful.
>
> I'm thinking if it would be helpful to include this count somewhere in
> /proc/xenomai as well (including total over all CPUs) as we don't
> always have the tracer on when the SMI bites / might have bitten. On
> one occasion, an overtemp condition on the CPU of one of our
> mainboards would trigger an SMI, which happened only after several
> days.
Well, in that case you can install msr-tools:
https://01.org/msr-tools
And run:
rdmsr 0x34
Of course, this requires CONFIG_X86_MSR in the kernel configuration,
which putting the count in /proc would avoid. But still, this would
be a bit redundant.
Regards.
--
Gilles.
https://click-hack.org
next prev parent reply other threads:[~2015-09-14 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 6:21 [Xenomai] SMI count polling Gilles Chanteperdrix
2015-09-14 7:41 ` Jeroen Van den Keybus
2015-09-14 7:45 ` Gilles Chanteperdrix [this message]
2015-09-14 8:09 ` Jeroen Van den Keybus
2015-09-14 17:27 ` Jan Kiszka
2015-09-14 19:01 ` Gilles Chanteperdrix
2015-09-14 19:07 ` Jan Kiszka
2015-09-14 19:59 ` Gilles Chanteperdrix
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=20150914074527.GA17701@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jeroen.vandenkeybus@gmail.com \
--cc=xenomai@xenomai.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 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.