From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] SMI count polling
Date: Mon, 14 Sep 2015 21:07:20 +0200 [thread overview]
Message-ID: <55F71AE8.9090706@siemens.com> (raw)
In-Reply-To: <20150914190123.GA27502@hermes.click-hack.org>
On 2015-09-14 21:01, Gilles Chanteperdrix wrote:
> On Mon, Sep 14, 2015 at 07:27:25PM +0200, Jan Kiszka wrote:
>> On 2015-09-14 10:09, Jeroen Van den Keybus wrote:
>>>> Well, in that case you can install msr-tools:
>>>> https://01.org/msr-tools
>>>
>>> Thanks for pointing out. I didn't know these existed. Always used
>>> direct msr device access.
>>>
>>>> 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.
>>>
>>> True, but given the frequent usage of SMI on many mainboards, their
>>> serious impact on realtime performance and SMIs being designed to
>>> remain undetected, a convenience function wouldn't hurt. Especially
>>> since I have the impression that it's an important stumbling stone for
>>> first-time users.
>>>
>>> Also, the total count would be useful since you would have to run
>>> rdmsr -p <CPU> 0x34 for every CPU in the system. I believe it's
>>> important to check for SMI occurrence on non-realtime CPUs as well,
>>> since I understand any of them might be handling them eventually ?
>>
>> Usually, the BIOS will force all cores into SMM: one core receives a
>> triggering SMI and then it sends SMIs as IPIs to the others. So the
>> counters increases on all cores, just with a minor delay.
>>
>> That said, having the rmdsr diagnosis documented would already be a
>> valuable addition for users.
>
> On the machine I was using where I discovered that tool, the value
> is indeed the same on all cores, and it incremented by the number of
> cores when . So, Jan, what do you think about
> adding code to the tracer generating an event when the counter
> value changes?
As we will have to poll for that event, it may be a little bit costly to
do this on every ipipe tracer entry. But then we could make it
configurable (via /proc) with default off - worth a try.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2015-09-14 19:07 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
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 [this message]
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=55F71AE8.9090706@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gilles.chanteperdrix@xenomai.org \
--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.