From: Juergen Gross <jgross@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xen.org, linux-kernel@vger.kernel.org
Cc: helgaas@kernel.org, christian.koenig@amd.com, JBeulich@suse.com
Subject: Re: [PATCH v3] xen/balloon: Mark unallocated host memory as UNUSABLE
Date: Wed, 20 Dec 2017 18:33:17 +0100 [thread overview]
Message-ID: <14100e87-ba75-3ebd-e39d-f1df2b298c8c@suse.com> (raw)
In-Reply-To: <1513778746-6155-1-git-send-email-boris.ostrovsky@oracle.com>
On 20/12/17 15:05, Boris Ostrovsky wrote:
> Commit f5775e0b6116 ("x86/xen: discard RAM regions above the maximum
> reservation") left host memory not assigned to dom0 as available for
> memory hotplug.
>
> Unfortunately this also meant that those regions could be used by
> others. Specifically, commit fa564ad96366 ("x86/PCI: Enable a 64bit BAR
> on AMD Family 15h (Models 00-1f, 30-3f, 60-7f)") may try to map those
> addresses as MMIO.
>
> To prevent this mark unallocated host memory as E820_TYPE_UNUSABLE (thus
> effectively reverting f5775e0b6116) and keep track of that region as
> a hostmem resource that can be used for the hotplug.
>
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
next prev parent reply other threads:[~2017-12-20 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 14:05 [PATCH v3] xen/balloon: Mark unallocated host memory as UNUSABLE Boris Ostrovsky
2017-12-20 17:33 ` Juergen Gross [this message]
2017-12-24 9:29 ` Christian König
2018-11-26 1:00 ` [Xen-devel] " Igor Druzhinin
2018-11-26 16:25 ` Boris Ostrovsky
2018-11-26 17:10 ` Igor Druzhinin
2018-11-26 19:42 ` Boris Ostrovsky
2018-11-26 19:57 ` Igor Druzhinin
2018-11-27 3:28 ` Boris Ostrovsky
2018-11-27 15:03 ` Igor Druzhinin
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=14100e87-ba75-3ebd-e39d-f1df2b298c8c@suse.com \
--to=jgross@suse.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=christian.koenig@amd.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xen.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