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]
Date:   Sat, 31 Oct 2020 11:05:45 +0100
From:   David Hildenbrand <>
To:     Christoph Hellwig <>,
        Mike Rapoport <>
Cc:     Sudarshan Rajagopalan <>,
        Mark Rutland <>,
        Catalin Marinas <>,
        Anshuman Khandual <>,, Steven Price <>,
        Suren Baghdasaryan <>,
        Greg Kroah-Hartman <>,
        Will Deacon <>,,
        Pratik Patel <>
Subject: Re: mm/memblock: export memblock_{start/end}_of_DRAM

On 31.10.20 10:18, Christoph Hellwig wrote:
> On Fri, Oct 30, 2020 at 10:38:42AM +0200, Mike Rapoport wrote:
>> What do you mean by "system memory block"? There could be a lot of
>> interpretations if you take into account memory hotplug, "mem=" option,
>> reserved and firmware memory.
>> I'd suggest you to describe the entire use case in more detail. Having
>> the complete picture would help finding a proper solution.
> I think we need the code for the driver trying to do this as an RFC
> submission.  Everything else is rather pointless.

Sharing RFCs is most probably not what people want when developing 
advanced hypervisor features :)

@Sudarshan, I recommend looking at the slides of the KVM Forum talk from 

It contains a nice summary of the state of art, and how "mem=", devdax, 
and dax_hmat can be used to tackle the issue in a hypervisor.


David / dhildenb

Powered by blists - more mailing lists