From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
George Dunlap <george.dunlap@citrix.com>, Wei Liu <wl@xen.org>,
Julien Grall <jgrall@amazon.com>, Henry Wang <Henry.Wang@arm.com>,
Alejandro Vallejo <alejandro.vallejo@cloud.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
Shawn Anastasio <sanastasio@raptorengineering.com>
Subject: Re: [PATCH v3 4/4] pdx: Add CONFIG_PDX_COMPRESSION as a common Kconfig option
Date: Mon, 25 Sep 2023 11:46:43 +0200 [thread overview]
Message-ID: <ZRFXA0dUHk5Rmlan@MacBookPdeRoger> (raw)
In-Reply-To: <b0296908-5081-5d34-8487-b8293eee97ca@suse.com>
On Mon, Sep 25, 2023 at 08:36:03AM +0200, Jan Beulich wrote:
> On 22.09.2023 22:03, Andrew Cooper wrote:
> > On 08/08/2023 2:02 pm, Alejandro Vallejo wrote:
> >> --- a/xen/common/Kconfig
> >> +++ b/xen/common/Kconfig
> >> @@ -23,6 +23,16 @@ config GRANT_TABLE
> >>
> >> If unsure, say Y.
> >>
> >> +config PDX_COMPRESSION
> >> + bool "PDX (Page inDeX) compression support" if EXPERT
> >
> > This still needs hiding on x86. The minimal hack for 4.18 is "if EXPERT
> > && !X86".
>
> If you insist on complete hiding and I insist on allowing it to be used by
> people who want to play with exotic hardware, then this won't go anywhere.
> I think I've come far enough with accepting a compromise, and so I think
> it's your turn now to also take a step from your original position.
Just because I'm not familiar with this, is there any x86 hardware
that has such sparse memory map that would benefit from PDX?
Wouldn't anyone doing bring up on such exotic hardware also likely need to
perform other adjustments to Xen, and hence commenting out the !X86 in
Kconfig be acceptable? (we would likely make it selectable at that
point if such platforms exist).
Thanks, Roger.
next prev parent reply other threads:[~2023-09-25 9:47 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é [this message]
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 ` [PATCH v3 0/4] Make PDX compression optional Alejandro Vallejo
2023-08-16 9:43 ` 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=ZRFXA0dUHk5Rmlan@MacBookPdeRoger \
--to=roger.pau@citrix.com \
--cc=Henry.Wang@arm.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=alejandro.vallejo@cloud.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgrall@amazon.com \
--cc=julien@xen.org \
--cc=sanastasio@raptorengineering.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.