On 24.07.2025 13:04, Roger Pau Monne wrote:
> The current setup (pdx_init_mask() and pdx_region_mask()) and init
> (pfn_pdx_hole_setup()) PDX compression functions are tailored to the
> existing PDX compression algorithm.
> 
> In preparation for introducing a new compression algorithm convert the
> setup and init functions to more generic interfaces that aren't tied to the
> compression in-use.  To accomplish this introduce a function that registers
> all the PFN RAM ranges, plus an init function.
> 
> This has the downside of requiring a static array to store such ranges
> ahead of being processed by the setup function, however it's the only way
> to pass all the possible information to the different compression setup
> functions without using per-compression specific setup functions.
> Per-arch compression setup also need to be adjusted to use the new
> interface.  There's a slight ordering adjustment, in that after PDX
> compression setup the caller will check whether all the RAM regions are
> properly covered by the newly setup compression, otherwise compression is
> disabled by resetting to the initial values.
> 
> No functional change intended in the resulting PDX compression values.
> 
> Signed-off-by: Roger Pau Monné <roger....@citrix.com>

Acked-by: Jan Beulich <jbeul...@suse.com>


Reply via email to