linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "clark.williams@gmail.com" <clark.williams@gmail.com>,
	"jkacur@redhat.com" <jkacur@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
	"Vineet Gupta" <Vineet.Gupta1@synopsys.com>
Subject: Re: [PATCH] Makefile: allow building selected tests with non-NPTL toolchain
Date: Thu, 15 Jan 2015 07:35:01 +0000	[thread overview]
Message-ID: <1421307300.3008.2.camel@synopsys.com> (raw)
In-Reply-To: <1415603814-7682-1-git-send-email-abrodkin@synopsys.com>

Hi Clark, John,

On Mon, 2014-11-10 at 10:16 +0300, Alexey Brodkin wrote:
> Some architectures are still stuck with non-NPTL toolchains.
> These are for example ARC, Blackfin, Xtensa etc.
> 
> Still rt-tests are very good benchmarks and it would be good to enable use of
> at least selected (those that will be built) tests on those architectures.
> 
> This change makes it possible to only build subset of tests that don't require
> NPTL calls.
> 
> By default behavior is not modified - all tests are built, but if one wants
> to build with non-NPTL toolchain just add "HAVE_NPTL=no" in command line
> or modify "HAVE_NPTL" variable right in Makefile and execute "make".
> 
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Vineet Gupta <vgupta@synopsys.com>
> Cc: Clark Williams <clark.williams@gmail.com>
> ---
>  Makefile | 11 ++++++++---
>  1 file changed, 8 insertions(+), 3 deletions(-)
> 
> diff --git a/Makefile b/Makefile
> index 318a5c6..675edf7 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1,8 +1,13 @@
>  VERSION_STRING = 0.89
>  
> -sources = cyclictest.c signaltest.c pi_stress.c rt-migrate-test.c	\
> -	  ptsematest.c sigwaittest.c svsematest.c pmqtest.c sendme.c 	\
> -	  pip_stress.c hackbench.c
> +HAVE_NPTL ?= yes
> +
> +ifeq ($(HAVE_NPTL),yes)
> +sources = cyclictest.c pi_stress.c pip_stress.c pmqtest.c rt-migrate-test.c
> +endif
> +
> +sources += signaltest.c ptsematest.c sigwaittest.c svsematest.c sendme.c \
> +	  hackbench.c
>  
>  TARGETS = $(sources:.c=)

I'm wondering if there's a chance to get this patch reviewed and if
there're no objections applied?

Regards,
Alexey

  reply	other threads:[~2015-01-15  7:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10  7:16 [PATCH] Makefile: allow building selected tests with non-NPTL toolchain Alexey Brodkin
2015-01-15  7:35 ` Alexey Brodkin [this message]
2015-01-15 18:45   ` Clark Williams

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=1421307300.3008.2.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=clark.williams@gmail.com \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.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).