On 9 April 2015 at 13:20, Paolo Bonzini <pbonz...@redhat.com> wrote: > This is an example of usage of attributes in a device model. It lets > you block flash writes unless the CPU is in secure mode. Enabling it > currently requires a -readconfig file: > > [global] > driver = "cfi.pflash01" > property = "secure" > value = "on" > > because the driver includes a "."; however, I plan to enable this through > the command line for the final version of the patches.
Are real flash devices ever wired up like this? I would expect boards which want to provide secure-mode only flash to do so by not giving any access at all to the device from the non-secure address space. (Supporting multiple AddressSpaces for ARM CPUs is the next thing on my todo list; as well as partitioning the flash this would allow secure-mode-only RAM and UARTs, for instance.) -- PMM
