mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	xen-devel@lists.xenproject.org,
	"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v2 4/7] xen: move max_pfn in xen_memory_setup() out of function scope
Date: Thu, 22 Aug 2024 13:38:00 +0200	[thread overview]
Message-ID: <e6095474-5000-410b-95b3-c0eeaf092042@suse.com> (raw)
In-Reply-To: <b9556863-1536-4310-8005-f92e8948356c@suse.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1278 bytes --]

On 20.08.24 10:44, Jan Beulich wrote:
> On 20.08.2024 10:20, Juergen Gross wrote:
>> Instead of having max_pfn as a local variable of xen_memory_setup(),
>> make it a static variable in setup.c instead. This avoids having to
>> pass it to subfunctions, which will be needed in more cases in future.
>>
>> Rename it to ini_nr_pages, as the value denotes the currently usable
>> number of memory pages as passed from the hypervisor at boot time.
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> Tested-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> 
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> 
> I wonder though why ...
> 
>> @@ -712,9 +713,9 @@ char * __init xen_memory_setup(void)
>>   	int op;
>>   
>>   	xen_parse_512gb();
>> -	max_pfn = xen_get_pages_limit();
>> -	max_pfn = min(max_pfn, xen_start_info->nr_pages);
>> -	mem_end = PFN_PHYS(max_pfn);
>> +	ini_nr_pages = xen_get_pages_limit();
>> +	ini_nr_pages = min(ini_nr_pages, xen_start_info->nr_pages);
> 
> ... this can't be just
> 
> 	ini_nr_pages = min(xen_get_pages_limit(), xen_start_info->nr_pages);

I just did a mechanical change for all uses of max_pfn.

I agree that your suggestion is an improvement, so I'll modify the
code.


Juergen


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2024-08-22 11:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20  8:20 [PATCH v2 0/7] xen: fix dom0 PV boot on some AMD machines Juergen Gross
2024-08-20  8:20 ` [PATCH v2 1/7] xen: use correct end address of kernel for conflict checking Juergen Gross
2024-08-20  8:29   ` Jan Beulich
2024-08-20  8:20 ` [PATCH v2 2/7] xen: introduce generic helper checking for memory map conflicts Juergen Gross
2024-08-20  8:35   ` Jan Beulich
2024-08-22 11:29     ` Jürgen Groß
2024-08-20  8:20 ` [PATCH v2 3/7] xen: move checks for e820 conflicts further up Juergen Gross
2024-08-20  8:40   ` Jan Beulich
2024-08-20  8:20 ` [PATCH v2 4/7] xen: move max_pfn in xen_memory_setup() out of function scope Juergen Gross
2024-08-20  8:44   ` Jan Beulich
2024-08-22 11:38     ` Jürgen Groß [this message]
2024-08-20  8:20 ` [PATCH v2 5/7] xen: add capability to remap non-RAM pages to different PFNs Juergen Gross
2024-08-20  9:38   ` Jan Beulich
2024-09-10  7:59     ` Jürgen Groß
2024-08-20  8:20 ` [PATCH v2 6/7] xen: allow mapping ACPI data using a different physical address Juergen Gross
2024-08-20  9:56   ` Jan Beulich
2024-09-10  8:15     ` Juergen Gross
2024-09-10  8:54       ` Jan Beulich
2024-08-20 17:37   ` kernel test robot
2024-08-20 19:39   ` kernel test robot
2024-08-20  8:20 ` [PATCH v2 7/7] xen: tolerate ACPI NVS memory overlapping with Xen allocated memory Juergen Gross
2024-08-20 10:23   ` Jan Beulich
2024-09-10  8:16     ` Jürgen Groß

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=e6095474-5000-410b-95b3-c0eeaf092042@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jbeulich@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marmarek@invisiblethingslab.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®