public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: John Kacur <jkacur@redhat.com>
Cc: Henning Schild <henning.schild@siemens.com>,
	RT <linux-rt-users@vger.kernel.org>,
	John Kacur <jkacur@gmail.com>,
	"Gary S. Robertson" <gary.robertson@linaro.org>,
	Clark Williams <williams@redhat.com>
Subject: Re: [PATCH] cyclictest: remove compatibilty hack for old libnuma, repairs "-a" for isolcpus
Date: Wed, 20 May 2015 21:54:15 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1505202153100.4225@nanos> (raw)
In-Reply-To: <alpine.LFD.2.10.1505201629400.7867@riemann>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 742 bytes --]

On Wed, 20 May 2015, John Kacur wrote:
> This is a terrible hack, but I'm afraid to remove it yet.
> Even systems as recent as Fedora 19 have a libnuma less than that.
> pm -qf /usr/lib64/libnuma.so
> numactl-devel-2.0.8-4.fc19.x86_64
> [jkacur@riemann rt-tests]$ cat /etc/fedora-release 
> Fedora release 19 (Schrödinger’s Cat)
> 
> This is causing problems for people who want to pin threads to 
> CPUs isolated with isolcpus=, so we do need to do something about.
> 
> I could perhaps accept an improved hack that tests whether the hack itself 
> is needed, until we have a better solution.

I'm not a great fan of it, but I think that rt-tests really needs
proper automake with proper tests for various bits and pieces.

Thanks,

	tglx

  reply	other threads:[~2015-05-20 19:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150427173222.04e8a1b1@md1em3qc>
2015-04-27 17:58 ` rt-tests, cyclictest libnuma and isolcpus Clark Williams
2015-05-20 12:58   ` [PATCH] cyclictest: remove compatibilty hack for old libnuma, repairs "-a" for isolcpus Henning Schild
2015-05-20 14:38     ` John Kacur
2015-05-20 19:54       ` Thomas Gleixner [this message]
     [not found]         ` <CAONaPpGpzzgjxQh+214cfOBVrqeX_yX=Kh981YyveHhTgyLA4A@mail.gmail.com>
2015-05-21 11:23           ` John Kacur
2015-05-21 11:11       ` Henning Schild
2015-05-21 12:23         ` Staffan Tjernstrom
2015-05-21 14:19           ` Henning Schild

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.DEB.2.11.1505202153100.4225@nanos \
    --to=tglx@linutronix.de \
    --cc=gary.robertson@linaro.org \
    --cc=henning.schild@siemens.com \
    --cc=jkacur@gmail.com \
    --cc=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --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