All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Vallejo <alejandro.vallejo@cloud.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: "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>,
	"George Dunlap" <george.dunlap@citrix.com>,
	"Jan Beulich" <jbeulich@suse.com>, "Wei Liu" <wl@xen.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH v3 0/4]  Make PDX compression optional
Date: Wed, 16 Aug 2023 10:36:09 +0100	[thread overview]
Message-ID: <64dc988b.df0a0220.d6d82.abb3@mx.google.com> (raw)
In-Reply-To: <20230808130220.27891-1-alejandro.vallejo@cloud.com>

On Tue, Aug 08, 2023 at 02:02:16PM +0100, Alejandro Vallejo wrote:
> Currently there's a CONFIG_HAS_PDX Kconfig option, but it's impossible to
> disable it because the whole codebase performs unconditional
> compression/decompression operations on addresses. This has the
> unfortunate side effect that systems without a need for compression still
> have to pay the performance impact of juggling bits on every pfn<->pdx
> conversion (this requires reading several global variables). This series
> attempts to:
> 
>   * Leave the state of pdx and pdx compression documented
>   * Factor out compression so it _can_ be removed through Kconfig
>   * Make it so compression is disabled on x86 and enabled on both Aarch32
>     and Aarch64 by default.
> 
> Series summary:
> 
> Patch 1 Moves hard-coded compression-related logic to helper functions
> Patch 2 Refactors all instances of regions being validated for pdx
>         compression conformance so it's done through a helper
> Patch 3 Non-functional reorder in order to simplify the patch 8 diff
> Patch 4 Adds new Kconfig option to compile out PDX compression and removes
>         the old CONFIG_HAS_PDX, as it was non removable
> 
> Already committed:
> 
> v1/patch 1 documents the current general understanding of the pdx concept and
>            pdx compression in particular
> v1/patch 3 Marks the pdx compression globals as ro_after_init
> v2/patch 1 Documents the differences between arm32 and arm64 directmaps
> 
> Alejandro Vallejo (4):
>   mm: Factor out the pdx compression logic in ma/va converters
>   mm/pdx: Standardize region validation wrt pdx compression
>   pdx: Reorder pdx.[ch]
>   pdx: Add CONFIG_PDX_COMPRESSION as a common Kconfig option

@Jan: Just making sure, are you generally ok with this series as-is?

Thanks,
Alejandro


  parent reply	other threads:[~2023-08-16  9:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08 13:02 [PATCH v3 0/4] Make PDX compression optional Alejandro Vallejo
2023-08-08 13:02 ` [PATCH v3 1/4] mm: Factor out the pdx compression logic in ma/va converters Alejandro Vallejo
2023-08-08 13:02 ` [PATCH v3 2/4] mm/pdx: Standardize region validation wrt pdx compression Alejandro Vallejo
2023-08-08 13:02 ` [PATCH v3 3/4] pdx: Reorder pdx.[ch] Alejandro Vallejo
2023-08-08 13:02 ` [PATCH v3 4/4] pdx: Add CONFIG_PDX_COMPRESSION as a common Kconfig option Alejandro Vallejo
2023-09-22 20:03   ` Andrew Cooper
2023-09-25  6:36     ` Jan Beulich
2023-09-25  9:46       ` Roger Pau Monné
2023-09-25  9:59         ` Jan Beulich
2023-09-25 10:01         ` Andrew Cooper
2023-09-25 10:15           ` Jan Beulich
2023-09-25 17:37     ` Shawn Anastasio
2023-10-06 13:20       ` Andrew Cooper
2023-08-16  9:36 ` Alejandro Vallejo [this message]
2023-08-16  9:43   ` [PATCH v3 0/4] Make PDX compression optional Jan Beulich
2023-08-16 11:12     ` Julien Grall
2023-08-16 11:27       ` Jan Beulich
2023-08-16 13:06         ` Julien Grall
2023-08-16 13:14           ` Jan Beulich
2023-08-16 13:38             ` Julien Grall

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=64dc988b.df0a0220.d6d82.abb3@mx.google.com \
    --to=alejandro.vallejo@cloud.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=bertrand.marquis@arm.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.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.