lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5cbe05c5-352f-32f5-a53e-aef59d8b2f59@suse.com>
Date:   Thu, 29 Nov 2018 17:55:52 +0100
From:   Juergen Gross <jgross@...e.com>
To:     Igor Druzhinin <igor.druzhinin@...rix.com>,
        boris.ostrovsky@...cle.com, xen-devel@...ts.xenproject.org,
        linux-kernel@...r.kernel.org
Cc:     jbeulich@...e.com
Subject: Re: [PATCH] Revert "xen/balloon: Mark unallocated host memory as
 UNUSABLE"

On 27/11/2018 21:58, Igor Druzhinin wrote:
> This reverts commit b3cf8528bb21febb650a7ecbf080d0647be40b9f.
> 
> That commit unintentionally broke Xen balloon memory hotplug with
> "hotplug_unpopulated" set to 1. As long as "System RAM" resource
> got assigned under a new "Unusable memory" resource in IO/Mem tree
> any attempt to online this memory would fail due to general kernel
> restrictions on having "System RAM" resources as 1st level only.
> 
> The original issue that commit has tried to workaround fa564ad96366
> ("x86/PCI: Enable a 64bit BAR on AMD Family 15h (Models 00-1f, 30-3f,
> 60-7f)") also got amended by the following 03a551734 ("x86/PCI: Move
> and shrink AMD 64-bit window to avoid conflict") which made the
> original fix to Xen ballooning unnecessary.
> 
> Signed-off-by: Igor Druzhinin <igor.druzhinin@...rix.com>

Pushed to xen/tip.git for-linus-4.20a


Juergen

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ