>> + /*
>> + * When FWB is unsupported KVM needs to do cache flushes
>> + * (via dcache_clean_inval_poc()) of the underlying memory. This is
>> + * only possible if the memory is already mapped into the kernel map.
>> + *
>> + * Outright reject as the cacheable device memory is not present in
>> + * the kernel map and not suitable for cache management.
>> + */
>> + if (cacheable_devmem && !stage2_has_fwb(pgt)) {
>> + ret = -EINVAL;
>> + goto out_unlock;
>> + }
>> +
>
> These new error reasons should at least be complemented by an
> equivalent check at the point where the memslot is registered. It
Understood. I can add such check in kvm_arch_prepare_memory_region().
> maybe OK to blindly return an error at fault time (because userspace
> has messed with the mapping behind our back), but there should at
> least be something telling a well behaved userspace that there is a
> bunch of combination we're unwilling to support.
How about WARN_ON() or BUG() for the faulty situation?
> Which brings me to the next point: FWB is not discoverable from
> userspace. How do you expect a VMM to know what it can or cannot do?
Good point. I am not sure if it can. I suppose you are concerned about error
during fault handling when !FWB without VMM having any clear indications
of the cause? Perhaps we can gracefully fall back to the default device mapping
in such case? But that would cause VM to crash as soon as it makes some
access violating DEVICE_nGnRE.
> M.
>
> --
> Without deviation from the norm, progress is not possible.
