Hi Stefano,
On 27/07/16 18:56, Stefano Stabellini wrote:
On Wed, 27 Jul 2016, Julien Grall wrote:
On 26/07/16 23:44, Stefano Stabellini wrote:
On Wed, 20 Jul 2016, Julien Grall wrote:
Currently, the check in get_page_from_gfn is using a blacklist. This is
very fragile because we may forgot to
On Wed, 27 Jul 2016, Julien Grall wrote:
> On 26/07/16 23:44, Stefano Stabellini wrote:
> > On Wed, 20 Jul 2016, Julien Grall wrote:
> > > Currently, the check in get_page_from_gfn is using a blacklist. This is
> > > very fragile because we may forgot to update the check when a new p2m
> > > type i
On 26/07/16 23:44, Stefano Stabellini wrote:
On Wed, 20 Jul 2016, Julien Grall wrote:
Currently, the check in get_page_from_gfn is using a blacklist. This is
very fragile because we may forgot to update the check when a new p2m
type is added.
To avoid any possible issue, use a whitelist. All
On Wed, 20 Jul 2016, Julien Grall wrote:
> Currently, the check in get_page_from_gfn is using a blacklist. This is
> very fragile because we may forgot to update the check when a new p2m
> type is added.
>
> To avoid any possible issue, use a whitelist. All type backed by a RAM
> page can could po
Currently, the check in get_page_from_gfn is using a blacklist. This is
very fragile because we may forgot to update the check when a new p2m
type is added.
To avoid any possible issue, use a whitelist. All type backed by a RAM
page can could potential be valid. The check is borrowed from x86.
Si
