linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Rachid Koucha <rachid.koucha@gmail.com>
Cc: williams@redhat.com, linux-rt-users@vger.kernel.org
Subject: Re: Little bug in cyclictest
Date: Thu, 15 Aug 2019 15:49:49 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.21.1908151544120.11513@planxty> (raw)
In-Reply-To: <7e292a1e-b52d-e8c6-37b0-05270df81539@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2045 bytes --]



On Wed, 14 Aug 2019, Rachid Koucha wrote:

> Find attach the patch file :
> 
> $ cd rt-tests
> $ patch -p1 < ../cyclictest_affinity_check.patch
> 
> On 14/08/2019 15:25, John Kacur wrote:
> >
> > On Wed, 14 Aug 2019, Rachid Koucha wrote:
> >
> >> Hi,
> >>
> >> First of all, many thanks for such useful tools.
> >>
> >> In the source code of cyclictest, I can see a mistake concerning the
> >> error checking of pthread_setaffinity_np():
> >>
> >> Upon error, pthread functions return an error ant not -1. So, the
> >> following code:
> >>
> >>     if (par->cpu != -1) {
> >>         CPU_ZERO(&mask);
> >>         CPU_SET(par->cpu, &mask);
> >>         thread = pthread_self();
> >>         if (pthread_setaffinity_np(thread, sizeof(mask), &mask) == -1)
> >>             warn("Could not set CPU affinity to CPU #%d\n",
> >>                  par->cpu);
> >>     }
> >>
> >> should be fixed as follow:
> >>
> >> int status;
> >>
> >>     if (par->cpu != -1) {
> >>         CPU_ZERO(&mask);
> >>         CPU_SET(par->cpu, &mask);
> >>         thread = pthread_self();
> >>         if ((status = pthread_setaffinity_np(thread, sizeof(mask), &mask)) != 0)
> >>             warn("Could not set CPU affinity to CPU #%d: %s (%d)\n",                  par->cpu, strerror(status), status);
> >>     }
> >>
> >>
> >> Regards,
> >>
> > Thanks, that looks correct. Please generate a patch and I'll apply it.
> >
> > John Kacur
> 

It would be easy for me to take the attachment and apply the patch, but if 
you want to work or play in the open source world, you have to follow 
certain rules for submitting patches.

The Linux Kernel source has a lot of documentation on how to do this, look 
here if you don't know how to access that

https://www.kernel.org/doc/html/v5.0/process/submitting-patches.html

So, you're going to need to describe the changes, and give your 
signed-off-by and no attachments, you have to use plain text.

Thanks!

John Kacur

      reply	other threads:[~2019-08-15 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14 12:07 Little bug in cyclictest Rachid Koucha
2019-08-14 13:25 ` John Kacur
2019-08-14 18:41   ` Rachid Koucha
2019-08-15 13:49     ` John Kacur [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=alpine.LFD.2.21.1908151544120.11513@planxty \
    --to=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rachid.koucha@gmail.com \
    --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).