From: Jon Masters <jonathan@jonmasters.org>
To: Wolfgang Steinwender <wolfgang@psysteme.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Problem with hwlat detector in smp_processor_id()
Date: Thu, 09 Jul 2009 10:36:37 -0400 [thread overview]
Message-ID: <1247150197.5512.13.camel@localhost.localdomain> (raw)
In-Reply-To: <4A55D53A.6040108@psysteme.de>
On Thu, 2009-07-09 at 13:32 +0200, Wolfgang Steinwender wrote:
> e = ring_buffer_consume(ring_buffer, smp_processor_id(), NULL);
>
> I'm wondering, because the seems to run at least for some people.
> Can it be a problem with my kernel?
Indeed. Can you post some more information - the config file as an
attachment, along with the specifics of what you recompiled?
Jon.
next prev parent reply other threads:[~2009-07-09 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 11:32 Problem with hwlat detector in smp_processor_id() Wolfgang Steinwender
2009-07-09 14:36 ` Carsten Emde
2009-08-10 14:07 ` Wolfgang Steinwender
2009-08-10 18:58 ` Clark Williams
2009-07-09 14:36 ` Jon Masters [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-22 9:18 John Kacur
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=1247150197.5512.13.camel@localhost.localdomain \
--to=jonathan@jonmasters.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=wolfgang@psysteme.de \
/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