From: Clark Williams <clark.williams@gmail.com>
To: Gary Robertson <gary.robertson@linaro.org>
Cc: Anders Roxell <anders.roxell@linaro.org>,
Mike Holmes <mike.holmes@linaro.org>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: Patches for cyclictest bug
Date: Tue, 25 Mar 2014 13:54:35 -0500 [thread overview]
Message-ID: <20140325135435.5acebb2f@sluggy> (raw)
In-Reply-To: <CAF7YWnyL2_pAcJ+8mUh++_kvh_rCXT3GimarN6F3WWyP0HWseg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
On Tue, 25 Mar 2014 13:30:35 -0500
Gary Robertson <gary.robertson@linaro.org> wrote:
> Mr. Williams,
>
> Linaro Networking Group have been using cyclictest in our kernel validation
> test suites as part of an OpenEmbedded root filesystem build. Between OE
> rt_tests build 0.86 and 0.87, our cyclictest lost its CPU affinity support.
>
> I have created a patch set which resolves this issue but I am unsure as to
> the best forum or mailing list to use in submitting the patches for the
> cyclictest sources cloned from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/clrkwllms/rt-tests.git
>
> If you will inform me as to the best place to email the patches I will send
> them for your consideration ASAP.
>
> Thanks,
>
> Gary Robertson
>
> Linaro Networking Group kernel tree maintainer
Gary,
Best place to discuss problems with the rt-tests group (which includes
cyclictest) is the linux-rt-users list (which I've CC'd).
We added a modification to affinity in the 0.87 version which allows
the user to specify an arbitrary set of cpus. It's entirely possible we
broke something in doing that.
What command line did you use that 0.87 broke?
Clark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
parent reply other threads:[~2014-03-25 18:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAF7YWnyL2_pAcJ+8mUh++_kvh_rCXT3GimarN6F3WWyP0HWseg@mail.gmail.com>]
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=20140325135435.5acebb2f@sluggy \
--to=clark.williams@gmail.com \
--cc=anders.roxell@linaro.org \
--cc=gary.robertson@linaro.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mike.holmes@linaro.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 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).