From: dmukhin@ford.com
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, andrew.cooper3@citrix.com,
anthony.perard@vates.tech, jbeulich@suse.com, julien@xen.org,
michal.orzel@amd.com, roger.pau@citrix.com, dmukhin@ford.com
Subject: Re: [PATCH v2 3/4] tests: use unit test fragment in PDX test
Date: Thu, 5 Feb 2026 17:42:03 -0800 [thread overview]
Message-ID: <aYVG6+jvmUrgOXYe@kraken> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2601231708190.7192@ubuntu-linux-20-04-desktop>
On Fri, Jan 23, 2026 at 05:09:05PM -0800, Stefano Stabellini wrote:
> On Sat, 10 Jan 2026, dmukhin@xen.org wrote:
> > From: Denis Mukhin <dmukhin@ford.com>
> >
> > Use the new make fragment to generate test harness code for the PDX unit test.
> >
> > Move <xen/bitops.h> earlier in xen/common/pdx.c to ensure harness.h is
> > included before triggering the #ifndef MAX_PFN_RANGES check when building a
> > unit test.
> >
> > Additionally, use real <xen/pdx.h> in harness.h instead of a locally
> > copied version.
> >
> > Update .gitignore to exclude generated test build-time dependencies.
> >
> > Not a functional change.
> >
> > Signed-off-by: Denis Mukhin <dmukhin@ford.com>
> > ---
> > Changes since v1:
[..]
> > -
> > -test-pdx-mask: CFLAGS += -DCONFIG_PDX_MASK_COMPRESSION
> > -test-pdx-offset: CFLAGS += -DCONFIG_PDX_OFFSET_COMPRESSION
>
> The test with -DCONFIG_PDX_OFFSET_COMPRESSION is lost?
Whoops, thanks for catching this!
next prev parent reply other threads:[~2026-02-06 1:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-11 4:11 [PATCH v2 0/4] tools/tests: test harness fragment dmukhin
2026-01-11 4:11 ` [PATCH v2 1/4] tests: fixup domid make fragment dmukhin
2026-01-12 11:16 ` Jan Beulich
2026-01-15 9:01 ` dmukhin
2026-01-24 0:59 ` Stefano Stabellini
2026-01-11 4:11 ` [PATCH v2 2/4] tests: introduce common fragment for unit tests dmukhin
2026-01-24 1:05 ` Stefano Stabellini
2026-01-11 4:11 ` [PATCH v2 3/4] tests: use unit test fragment in PDX test dmukhin
2026-01-24 1:09 ` Stefano Stabellini
2026-02-06 1:42 ` dmukhin [this message]
2026-01-11 4:11 ` [PATCH v2 4/4] tests: use unit test fragment in vPCI test dmukhin
2026-01-24 1:25 ` Stefano Stabellini
2026-02-06 1:47 ` dmukhin
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=aYVG6+jvmUrgOXYe@kraken \
--to=dmukhin@ford.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--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.