linux-kernel - Re: [PATCH v3 1/1] Create debugfs file with hyper-v balloon usage information

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: <e3f418a9-97c4-0e8c-4446-b85fefd2cad8@virtuozzo.com>
Date:   Wed, 7 Sep 2022 11:15:28 +0300
From:   Alexander Atanasov <alexander.atanasov@...tuozzo.com>
To:     "Michael Kelley (LINUX)" <mikelley@...rosoft.com>,
        Wei Liu <wei.liu@...nel.org>
Cc:     KY Srinivasan <kys@...rosoft.com>,
        Haiyang Zhang <haiyangz@...rosoft.com>,
        Stephen Hemminger <sthemmin@...rosoft.com>,
        Dexuan Cui <decui@...rosoft.com>,
        "kernel@...nvz.org" <kernel@...nvz.org>,
        "linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/1] Create debugfs file with hyper-v balloon usage
 information

Hello,

On 3.09.22 7:37, Michael Kelley (LINUX) wrote:
> 
> Alexander -- I finally caught up on the long discussion of balloon
> driver reporting that occurred over much of August.  I think your
> original plan had been for each of the balloon driver to report
> useful information in debugfs.  But as a result of the discussion,
> it looks like virtio-balloon will be putting the information in
> /proc/meminfo.  If that's the case, it seems like we should
> drop these changes to the Hyper-V balloon driver,  and have
> the Hyper-V balloon driver take the same approach as
> virtio-balloon.
> 
> These Hyper-V balloon driver changes have already gone
> into 6.0-rc1.  If we're going to drop them, we should do
> the revert before 6.0 is done.
> 
> Thoughts?


There is a lot of information that would not go into /proc/meminfo.
vmware have only one file with all, virtio have separate file for 
features to expose. HV doesn't have other files so i think file is still 
useful. Only the memory in kB will go into the /proc/meminfo - 
pages/page sizes would not. But i am not sure how to handle the 
situation since i guess it will take time for the MM guys to decide - 
there is currently only one Ack on the series.



-- 
Regards,
Alexander Atanasov