linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: GeunSik Lim <leemgs1@gmail.com>
To: Clark Williams <williams@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: cyclictest - fix comparison about flexible word counts of available_tracers file.
Date: Mon, 6 Apr 2009 11:49:58 +0900	[thread overview]
Message-ID: <49b7c2350904051949m3a52d270j912b56693683e27c@mail.gmail.com> (raw)
In-Reply-To: <20090405095001.6dc50fbc@torg>

Dear Clark

Thanks your patching.

Since I didn't have IRQSOFF or
> PREEMPTOFF set in my kernel, those tracers weren't available and fscanf
> never returned EOF (it kept returning the "nop" tracer).

Clark. I think that Your approach is right.

In fact , I also thought  this case that  a developer disable
PREEMPTOFF or IRQSOFF on "#>make menuconfig" setting menu.
As you know, Most peoples will use -P or -I option when they enabled
PREEMPTOFF or IRQSOFF in Linux Kernel just.

But, Exception Handling is important as your explanation.
Thanks again.


2009/4/5 Clark Williams <williams@redhat.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sun, 5 Apr 2009 15:45:33 +0900
> GeunSik Lim <leemgs1@gmail.com> wrote:
>
>> Dear Thomas,
>>
>> I found bug at settracer function of cyclictest.c source (rt-test ver 0.33).
>> settracer func use 10 times in the for() statement to searching tracer
>> like preemptoff , irqsoff , preemptirqsoff.
>> But, I think that we have to consider 10+ words in the available_tracers file.
>>
>
> GeunSik,
>
> Good catch!  I applied your patch, but then found a bug in either
> fscanf or debugfs (probably debugfs). Since I didn't have IRQSOFF or
> PREEMPTOFF set in my kernel, those tracers weren't available and fscanf
> never returned EOF (it kept returning the "nop" tracer). So I reworked
> your patch to read everything in and parse it using strtok(3).
>
> The git tree has been updated and an rt-tests-0.34.tar.gz tarball is
> available at:
>
> http://www.kernel.org/pub/linux//kernel/people/clrkwllms/rt-tests/
>
> Clark
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.10 (GNU/Linux)
>
> iEYEARECAAYFAknYxR4ACgkQHyuj/+TTEp3TNwCbBNrEHMLjPmAS6JciwjyXWqME
> wpcAn3+nUGdOwCJR6sFGfwundPtaITrk
> =dT+3
> -----END PGP SIGNATURE-----
>



-- 
Regards,
GeunSik Lim
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2009-04-06  2:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-05  6:45 cyclictest - fix comparison about flexible word counts of available_tracers file GeunSik Lim
2009-04-05 14:05 ` Thomas Gleixner
2009-04-05 14:50 ` Clark Williams
2009-04-06  2:49   ` GeunSik Lim [this message]

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=49b7c2350904051949m3a52d270j912b56693683e27c@mail.gmail.com \
    --to=leemgs1@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).