linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: RT <linux-rt-users@vger.kernel.org>, Christian Eggers <ceggers@arri.de>
Cc: Daniel Wagner <wagi@monom.org>,
	Kurt Kanzenbach <kurt.kanzenbach@linutronix.de>,
	Clark Williams <williams@redhat.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	John Kacur <jkacur@redhat.com>
Subject: [PATCH 0/2] Fix for machines without numa
Date: Mon, 22 Feb 2021 17:07:48 -0500	[thread overview]
Message-ID: <20210222220750.12911-1-jkacur@redhat.com> (raw)

Trying to return the code to a state where numa is required at compile
time but not at runtime

- The first patch should allow cyclictest to run on a machine
without numa.

- The second patch is a clean-up of some old code

The code is pushed in git to branch unstable/devel/no-numa-runtime
so that people can test before I integrate the code back in the main
branch

Thanks

John

John Kacur (2):
  rt-tests: Don't assume numa is available at runtime
  rt-tests: remove rt_numa_bitmask_count in rt_numa.h

 src/cyclictest/cyclictest.c |  8 ++------
 src/cyclictest/rt_numa.h    | 12 ------------
 src/lib/rt-numa.c           | 17 +++++++++++------
 src/signaltest/signaltest.c |  8 ++------
 4 files changed, 15 insertions(+), 30 deletions(-)

-- 
2.26.2


             reply	other threads:[~2021-02-22 22:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 22:07 John Kacur [this message]
2021-02-22 22:07 ` [PATCH 1/2] rt-tests: Don't assume numa is available at runtime John Kacur
2021-02-22 22:07 ` [PATCH 2/2] rt-tests: remove rt_numa_bitmask_count in rt_numa.h John Kacur
2021-02-24  9:25 ` [PATCH 0/2] Fix for machines without numa Kurt Kanzenbach
2021-02-25  3:36   ` 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=20210222220750.12911-1-jkacur@redhat.com \
    --to=jkacur@redhat.com \
    --cc=bigeasy@linutronix.de \
    --cc=ceggers@arri.de \
    --cc=kurt.kanzenbach@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=wagi@monom.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;
as well as URLs for NNTP newsgroup(s).