On 22 February 2015 at 06:56, Rob Herring <robherring2@xxxxxxxxx> wrote: > On Thu, Feb 19, 2015 at 1:03 PM, Christoffer Dall > <christoffer.dall@xxxxxxxxxx> wrote: >> It matters if you want to ensure that the 64K page you are assigning to >> a guest for the GIC virtual CPU interface contains only GIC virtual CPU >> mappings, and not other random stuff that the guest is not allowed to >> touch. > > Good point. > >> How else should this be enforced? > > Rely on correct h/w design? You'll have to repeat this every time you > want to do pass-thru of a device. The idea is that the device tree lets us describe whether the hardware design is correct or not :-) > What do you do if 64K mapping is not supported? Fallback to emulation > of the CPU interface? In this case KVM can't be supported -- use 4K host pages with this hardware, or don't use KVM... -- PMM -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
