From: Juergen Gross <jgross@suse.com>
To: David Vrabel <david.vrabel@citrix.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
konrad.wilk@oracle.com, boris.ostrovsky@oracle.com,
daniel.kiper@oracle.com
Subject: Re: [Xen-devel] [PATCH 2/2] xen: before ballooning hotplugged memory, set frames to invalid
Date: Thu, 19 Mar 2015 18:19:50 +0100 [thread overview]
Message-ID: <550B0536.2000104@suse.com> (raw)
In-Reply-To: <550AF6EE.9010404@citrix.com>
On 03/19/2015 05:18 PM, David Vrabel wrote:
> On 19/03/15 14:31, Juergen Gross wrote:
>> Commit 25b884a83d487fd62c3de7ac1ab5549979188482 ("x86/xen: set
>> regions above the end of RAM as 1:1") introduced a regression.
>>
>> To be able to add memory pages which were added via memory hotplug to
>> a pv domain, the pages must be "invalid" instead of "identity" in the
>> p2m list before they can be added.
> [...]
>> --- a/drivers/xen/balloon.c
>> +++ b/drivers/xen/balloon.c
>> @@ -221,15 +221,24 @@ static bool balloon_is_inflated(void)
>>
>> static enum bp_state reserve_additional_memory(long credit)
>> {
>> - int nid, rc;
>> + int nid, rc = 0;
>> u64 hotplug_start_paddr;
>> unsigned long balloon_hotplug = credit;
>> + unsigned long pfn;
>>
>> hotplug_start_paddr = PFN_PHYS(SECTION_ALIGN_UP(max_pfn));
>> balloon_hotplug = round_up(balloon_hotplug, PAGES_PER_SECTION);
>> nid = memory_add_physaddr_to_nid(hotplug_start_paddr);
>>
>> - rc = add_memory(nid, hotplug_start_paddr, balloon_hotplug << PAGE_SHIFT);
>> + for (pfn = PFN_DOWN(hotplug_start_paddr);
>> + !rc && pfn < PFN_DOWN(hotplug_start_paddr) + balloon_hotplug;
>> + pfn++)
>> + if (!set_phys_to_machine(pfn, INVALID_P2M_ENTRY))
>> + rc = 1;
>
> rc = -ENOMEM;
I used the value 1 on purpose to be able to identify the case by the
value printed in the warning below.
> break;
Why? !rc is already tested in the for() clause.
>
>> +
>> + if (!rc)
>> + rc = add_memory(nid, hotplug_start_paddr,
>> + balloon_hotplug << PAGE_SHIFT);
>
> Use else here.
Huh? I want the message to be printed if either set_phys_to_machine()
or add_memory() failed.
>
>> if (rc) {
>> pr_warn("Cannot add additional memory (%i)\n", rc);
>>
Juergen
next prev parent reply other threads:[~2015-03-19 17:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 14:31 [PATCH 0/2] xen: fix regressions regarding memory hotplug in pv domains Juergen Gross
2015-03-19 14:31 ` [PATCH 1/2] xen: prepare p2m list for memory hotplug Juergen Gross
2015-03-19 15:53 ` Boris Ostrovsky
2015-03-19 17:01 ` Juergen Gross
2015-03-19 16:14 ` Daniel Kiper
2015-03-19 17:05 ` Juergen Gross
2015-03-19 17:05 ` Juergen Gross
2015-03-19 16:18 ` [Xen-devel] " David Vrabel
2015-03-19 16:18 ` David Vrabel
2015-03-19 17:16 ` Juergen Gross
2015-03-19 17:22 ` David Vrabel
2015-03-19 17:22 ` David Vrabel
2015-03-19 19:15 ` Paul Bolle
2015-03-19 14:31 ` [PATCH 2/2] xen: before ballooning hotplugged memory, set frames to invalid Juergen Gross
2015-03-19 16:18 ` [Xen-devel] " David Vrabel
2015-03-19 16:18 ` David Vrabel
2015-03-19 17:19 ` Juergen Gross [this message]
2015-03-19 17:40 ` David Vrabel
2015-03-19 17:40 ` David Vrabel
2015-03-19 16:21 ` Daniel Kiper
2015-03-19 17:22 ` Juergen Gross
2015-03-19 18:40 ` Daniel Kiper
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=550B0536.2000104@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=daniel.kiper@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/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.