On Fri, Jun 17, 2016 at 03:38:53PM +0200, Paolo Bonzini wrote: > Making the guest's phys-bits larger than host-phys-bits would be okay if > you reserve the area in the e820 and assume the guest doesn't touch it.
How would it touch it if there's no RAM there? PCI BARs is the only thing that comes to mind, but we fix that by making a sane _CRS. What did I miss? > But it is not a great idea too, because e820 describes RAM, so you're > telling the guest "look, there's 64 TB of reserved RAM up there". > > >> 3) Is it better to stick to sizes that correspond to real hardware > >> if you can? For example I don't know of any machines with 37 bits > >> - in practice I think it's best to stick with sizes that correspond > >> to some real hardware. > > > > Yeah, "as small as possible" could be actually "the smallest > > possible value from a set of known-to-exist values". e.g. if we > > find out that we need 37 bits, it's probably better to simply use > > 39 bits. > > > > Choosing from a smaller set of values also makes corner cases > > (like the example above) less likely to happen. > > Not really, because any value that doesn't match the host is > problematic, albeit in different ways. > > Paolo
