linux-kernel - Re: [PATCH v2 22/23] mm: rename CONFIG_MEMORY_BALLOON -> CONFIG

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <71f211f0-498b-4829-8370-0c22885856d5@kernel.org>
Date: Thu, 15 Jan 2026 17:56:37 +0100
From: "David Hildenbrand (Red Hat)" <david@...nel.org>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
 linux-kernel@...r.kernel.org, linux-mm@...ck.org,
 linuxppc-dev@...ts.ozlabs.org,
 Broadcom internal kernel review list
 <bcm-kernel-feedback-list@...adcom.com>, linux-doc@...r.kernel.org,
 virtualization@...ts.linux.dev, Andrew Morton <akpm@...ux-foundation.org>,
 Oscar Salvador <osalvador@...e.de>, "Liam R. Howlett"
 <Liam.Howlett@...cle.com>, Vlastimil Babka <vbabka@...e.cz>,
 Mike Rapoport <rppt@...nel.org>, Suren Baghdasaryan <surenb@...gle.com>,
 Michal Hocko <mhocko@...e.com>, Jonathan Corbet <corbet@....net>,
 Madhavan Srinivasan <maddy@...ux.ibm.com>,
 Michael Ellerman <mpe@...erman.id.au>, Nicholas Piggin <npiggin@...il.com>,
 Christophe Leroy <christophe.leroy@...roup.eu>, Arnd Bergmann
 <arnd@...db.de>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Jerrin Shaji George <jerrin.shaji-george@...adcom.com>,
 Jason Wang <jasowang@...hat.com>, Xuan Zhuo <xuanzhuo@...ux.alibaba.com>,
 Eugenio Pérez <eperezma@...hat.com>, Zi Yan <ziy@...dia.com>
Subject: Re: [PATCH v2 22/23] mm: rename CONFIG_MEMORY_BALLOON ->
 CONFIG_BALLOON

On 1/15/26 17:53, Michael S. Tsirkin wrote:
> On Thu, Jan 15, 2026 at 05:33:56PM +0100, David Hildenbrand (Red Hat) wrote:
>> I'll note that the spec also defines a "DEVICE ID of Virtio Cpu balloon device as 47". But
>> no changes really happened in the spec with that for the last two years (only the
>> id is reserved).
>>
>>
>> [1] https://docs.oasis-open.org/virtio/virtio/v1.4/virtio-v1.4.html#x1-4260001
> 
> 
> Maybe that's a good reason to keep calling it "memory balloon".
> 
> And hey, there's also the floating, pops easily kind and maybe someone
> will use those with linux in some way :)

There is only one true balloon ;) the others can specify it as 
CPU_BALLOON. If that ever sees the light of day.

-- 
Cheers

David