Christoph Hellwig <h...@infradead.org> writes:
> On Fri, Apr 06, 2018 at 03:41:39PM -0700, Dan Williams wrote:
>> Yes, but the trust interface definition is what is missing, especially
>> when we consider memmap=ss!nn and qemu-kvm. For example do we turn off
>> DAX and/or MAP_SYNC on all platforms that don't provide a positive "I
>> have ADR" indication (ACPI 6.2 Section 184.108.40.206 NFIT Platform
>> Capabilities Structure)?
> Sounds like a default.
Which do you turn off? DAX or MAP_SYNC (or both)?
Systems that support ACPI versions earlier than 6.2 could provide
flush hint addresses. In that case, we could assume no ADR, and turn
off MAP_SYNC, but still allow DAX. Note that I'm not aware of any
hardware that actually falls into this category.
Platforms prior to 6.2 that don't support flush hints are currently
assumed to implement ADR. This proposal would change that default.
>> Require opt-in when the user has trust in the hardware config that
>> the kernel can't verify?
> And that sounds like a good config nob ontop of that default.
Well, we could also make a white-list for known good platforms. I
assume HPE's systems would be on that list. Otherwise we'd have to cook
up udev rules, I guess?
Dan, is this something you're working on now?
Linux-nvdimm mailing list