From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Michal Orzel <michal.orzel@amd.com>
Cc: xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Anthony PERARD <anthony.perard@vates.tech>,
Jan Beulich <jbeulich@suse.com>,
Timothy Pearson <tpearson@raptorengineering.com>,
Teddy Astie <teddy.astie@vates.tech>
Subject: Re: [PATCH v2 1/2] xen/pdx: account for frametable_base_pdx in generic pdx_to_page/page_to_pdx
Date: Mon, 4 May 2026 17:28:29 +0200 [thread overview]
Message-ID: <afi7HUFoDYabM9VV@macbook.local> (raw)
In-Reply-To: <20260430125103.401811-2-michal.orzel@amd.com>
On Thu, Apr 30, 2026 at 02:51:02PM +0200, Michal Orzel wrote:
> The generic pdx_to_page() and page_to_pdx() macros in xen/pdx.h assume
> the frame table starts at PDX 0, which is only true on x86. ARM
> uses a non-zero frametable_base_pdx to offset into the frame table (PPC also
> defines it).
>
> Fix the generic macros to subtract/add frametable_base_pdx, defaulting
> to 0 when the arch does not define it. This makes the generic macros
> correct for all architectures, even though they are only used on x86
> today.
Hm, I assume this offset was added because the original mask PDX
compression won't (usually) compress the gap between 0 and the start
of RAM. However the newish offset PDX compression should be able to
compress from 0 to start of RAM, and hence you don't need to apply
an extra PDX offset there?
If that's indeed the case it might be better to integrate
frametable_base_pdx into the mask compression algorithm itself, so
that on some arches it's a mask plus a decrease.
Thanks, Roger.
next prev parent reply other threads:[~2026-05-04 15:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 12:51 [PATCH v2 0/2] xen/arm: Improve frametable allocation Michal Orzel
2026-04-30 12:51 ` [PATCH v2 1/2] xen/pdx: account for frametable_base_pdx in generic pdx_to_page/page_to_pdx Michal Orzel
2026-05-01 9:41 ` Luca Fancellu
2026-05-01 17:08 ` Stefano Stabellini
2026-05-04 15:28 ` Roger Pau Monné [this message]
2026-05-05 6:48 ` Orzel, Michal
2026-05-05 7:13 ` Roger Pau Monné
2026-05-05 7:35 ` Orzel, Michal
2026-05-05 8:34 ` Roger Pau Monné
2026-05-05 10:40 ` Jan Beulich
2026-05-05 10:46 ` Orzel, Michal
2026-05-05 10:49 ` Jan Beulich
2026-05-05 11:46 ` Orzel, Michal
2026-05-05 12:15 ` Roger Pau Monné
2026-05-05 14:38 ` Orzel, Michal
2026-05-05 13:00 ` Jan Beulich
2026-05-05 14:44 ` Orzel, Michal
2026-05-05 15:20 ` Roger Pau Monné
2026-05-05 13:05 ` Jan Beulich
2026-05-05 14:52 ` Orzel, Michal
2026-05-05 16:11 ` Jan Beulich
2026-05-06 7:01 ` Orzel, Michal
2026-04-30 12:51 ` [PATCH v2 2/2] xen/arm: skip holes in physical address space when setting up frametable Michal Orzel
2026-05-01 15:00 ` Luca Fancellu
2026-05-01 17:08 ` Stefano Stabellini
2026-05-04 14:46 ` Orzel, Michal
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=afi7HUFoDYabM9VV@macbook.local \
--to=roger.pau@citrix.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=bertrand.marquis@arm.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=teddy.astie@vates.tech \
--cc=tpearson@raptorengineering.com \
--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.