From: Anthony PERARD <anthony@xenproject.org>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Andrew Cooper <andrew.cooper3@citrix.com>,
Michal Orzel <michal.orzel@amd.com>,
Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH v2 6/8] test/pdx: add PDX compression unit tests
Date: Tue, 24 Jun 2025 15:37:34 +0200 [thread overview]
Message-ID: <aFqqHtRPmbndhcnK@l14> (raw)
In-Reply-To: <20250620111130.29057-7-roger.pau@citrix.com>
On Fri, Jun 20, 2025 at 01:11:28PM +0200, Roger Pau Monne wrote:
> +.PHONY: run
> +run: $(TARGETS)
> +ifeq ($(CC),$(HOSTCC))
> + for test in $? ; do \
> + ./$$test ; \
> + done
You need to add `set -e` or the exit value from the tested binary might
be ignored. This `run` target only failed if the last test binary return
a failure.
> +else
> + $(warning HOSTCC != CC, will not run test)
> +endif
> +
> +.PHONY: clean
> +clean:
> + $(RM) -- *.o $(TARGETS) $(DEPS_RM) pdx.c pdx.h
Is this "pdx.c" left over from version? It doesn't seems to be generated
by this makefile.
> +
> +pdx.h: $(XEN_ROOT)/xen/include/xen/pdx.h
> + sed -E -e '/^#[[:space:]]?include/d' <$< >$@
Why allow only zero or one space characters between '#' and
"include"? Why not used '*' instead of '?' ?
Thanks,
--
Anthony PERARD
next prev parent reply other threads:[~2025-06-24 13:37 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 11:11 [PATCH v2 0/8] pdx: introduce a new compression algorithm Roger Pau Monne
2025-06-20 11:11 ` [PATCH v2 1/8] x86/pdx: simplify calculation of domain struct allocation boundary Roger Pau Monne
2025-06-24 13:05 ` Jan Beulich
2025-06-25 15:14 ` Roger Pau Monné
2025-06-20 11:11 ` [PATCH v2 2/8] kconfig: turn PDX compression into a choice Roger Pau Monne
2025-06-24 13:13 ` Jan Beulich
2025-06-26 7:49 ` Roger Pau Monné
2025-06-26 12:33 ` Jan Beulich
2025-06-20 11:11 ` [PATCH v2 4/8] pdx: introduce command line compression toggle Roger Pau Monne
2025-06-24 13:40 ` Jan Beulich
2025-06-25 15:46 ` Roger Pau Monné
2025-06-25 16:00 ` Jan Beulich
2025-06-25 17:45 ` Roger Pau Monné
2025-06-26 6:17 ` Jan Beulich
2025-06-20 11:11 ` [PATCH v2 5/8] pdx: allow per-arch optimization of PDX conversion helpers Roger Pau Monne
2025-06-24 13:51 ` Jan Beulich
2025-06-25 15:51 ` Roger Pau Monné
2025-06-25 16:04 ` Jan Beulich
2025-06-20 11:11 ` [PATCH v2 6/8] test/pdx: add PDX compression unit tests Roger Pau Monne
2025-06-24 13:37 ` Anthony PERARD [this message]
2025-06-25 15:55 ` Roger Pau Monné
2025-06-20 11:11 ` [PATCH v2 7/8] pdx: move some helpers in preparation for new compression Roger Pau Monne
2025-06-24 13:52 ` Jan Beulich
2025-06-20 11:11 ` [PATCH v2 8/8] pdx: introduce a new compression algorithm based on region offsets Roger Pau Monne
2025-06-24 16:16 ` Jan Beulich
2025-06-25 16:24 ` Roger Pau Monné
2025-06-26 7:35 ` Jan Beulich
2025-06-27 14:51 ` Roger Pau Monné
2025-06-29 14:36 ` Jan Beulich
2025-07-01 7:26 ` Roger Pau Monné
2025-06-30 6:34 ` Jan Beulich
2025-07-01 15:49 ` Roger Pau Monné
2025-07-01 16:01 ` Jan Beulich
[not found] ` <20250620111130.29057-4-roger.pau@citrix.com>
2025-06-24 13:32 ` [PATCH v2 3/8] pdx: provide a unified set of unit functions Jan Beulich
2025-06-25 15:32 ` Roger Pau Monné
2025-06-28 2:08 ` [PATCH v2 0/8] pdx: introduce a new compression algorithm Stefano Stabellini
2025-06-30 15:02 ` Roger Pau Monné
2025-07-01 1:50 ` Stefano Stabellini
2025-07-01 3:33 ` Stefano Stabellini
2025-07-01 6:05 ` Jan Beulich
2025-07-01 20:46 ` Stefano Stabellini
2025-07-02 6:08 ` Jan Beulich
2025-07-02 6:32 ` Jan Beulich
2025-07-02 6:53 ` Roger Pau Monné
2025-07-02 7:00 ` Roger Pau Monné
2025-07-02 7:52 ` Orzel, Michal
2025-07-02 8:26 ` Roger Pau Monné
2025-07-02 8:49 ` Julien Grall
2025-07-02 8:54 ` Orzel, Michal
2025-07-02 9:45 ` Roger Pau Monné
2025-07-03 0:22 ` Stefano Stabellini
2025-07-03 0:19 ` Stefano Stabellini
2025-07-02 8:45 ` Julien Grall
2025-07-03 8:42 ` Roger Pau Monné
2025-07-03 18:04 ` Stefano Stabellini
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=aFqqHtRPmbndhcnK@l14 \
--to=anthony@xenproject.org \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.