>> Will simply always be interpreted. Should not affect the CPU model. > > Bear with me, it was a long day: > > Would it make sense to force user space to configure HPAGE before asking > for model data, so that we can remove these model bits already from > kernel side and wouldn't need extensive handling on two points? It doesn't make any difference though. The problem is that we will always have to probe the CPU model without knowing which type of memory we will have. This is than reported e.g. via "virsh domcapabilities". So it is better to do like "you're supporting cmma" while you actually silently disable it when huge pages are used. Otherwise, the expanded host model won't be able to run. Please note that this is not a problem for migration: We expect the same command line, so also the same "lying about CMMA" on both sides. Wonder if there would be any way to fake CMMA support when not having PGSTE - at least in a sane way. (always intercept and ignore or sth like that - that would make it even easier to handle) -- Thanks, David / dhildenb -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
