Hi Stefano,
On 14/08/2019 23:40, Stefano Stabellini wrote:
On Tue, 13 Aug 2019, Julien Grall wrote:
On 8/13/19 3:34 PM, Volodymyr Babchuk wrote:
Stefano Stabellini writes:
On a side note, the check is still incorrect here because you would allow
/reserved-memory@... or /reserved-memory-test
On Tue, 13 Aug 2019, Julien Grall wrote:
> On 8/13/19 3:34 PM, Volodymyr Babchuk wrote:
> >
> > Stefano Stabellini writes:
> >
> > > Don't allow reserved-memory regions to be remapped into any unprivileged
> > > guests, until reserved-memory regions are properly supported in Xen. For
> > > now,
Hi,
On 8/13/19 3:34 PM, Volodymyr Babchuk wrote:
Stefano Stabellini writes:
Don't allow reserved-memory regions to be remapped into any unprivileged
guests, until reserved-memory regions are properly supported in Xen. For
now, do not call iomem_permit_access on them, because giving
Stefano Stabellini writes:
> Don't allow reserved-memory regions to be remapped into any unprivileged
> guests, until reserved-memory regions are properly supported in Xen. For
> now, do not call iomem_permit_access on them, because giving
> iomem_permit_access to dom0 means that the toolstack
Don't allow reserved-memory regions to be remapped into any unprivileged
guests, until reserved-memory regions are properly supported in Xen. For
now, do not call iomem_permit_access on them, because giving
iomem_permit_access to dom0 means that the toolstack will be able to
assign the region to a
