[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH for-4.19? v5 09/10] xen/x86: Disallow creating domains with altp2m enabled and altp2m.nr == 0

To: Petr Beneš <w1benny@xxxxxxxxx>
From: Jan Beulich <jbeulich@xxxxxxxx>
Date: Thu, 6 Jun 2024 09:57:46 +0200
Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 06 Jun 2024 07:57:54 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 02.06.2024 22:04, Petr Beneš wrote:
> From: Petr Beneš <w1benny@xxxxxxxxx>
> 
> Since libxl finally sends the altp2m.nr value, we can remove the previously
> introduced temporary workaround.
> 
> Creating domain with enabled altp2m while setting altp2m.nr == 0 doesn't
> make sense and it's probably not what user wants.

Yet: Do we need separate count and flag anymore? Can't "nr != 0"
take the place of the flag being true?

Jan

Follow-Ups:
- Re: [PATCH for-4.19? v5 09/10] xen/x86: Disallow creating domains with altp2m enabled and altp2m.nr == 0
  - From: Petr Beneš

References:
- [PATCH for-4.19? v5 00/10] x86: Make MAX_ALTP2M configurable
  - From: Petr Beneš
- [PATCH for-4.19? v5 09/10] xen/x86: Disallow creating domains with altp2m enabled and altp2m.nr == 0
  - From: Petr Beneš

Prev by Date: Re: [XEN PATCH v1] x86/cpufreq: separate powernow/hwp cpufreq code
Next by Date: Re: [PATCH v3 3/3] ui+display: rename is_buffer_shared() -> surface_is_allocated()
Previous by thread: [PATCH for-4.19? v5 09/10] xen/x86: Disallow creating domains with altp2m enabled and altp2m.nr == 0
Next by thread: Re: [PATCH for-4.19? v5 09/10] xen/x86: Disallow creating domains with altp2m enabled and altp2m.nr == 0
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.