Re: [Xen-devel] [PATCH v2 3/3] xen: fix hvm guest with kaslr enabled

2017-08-08 Thread Andrew Cooper
On 28/07/17 11:23, Juergen Gross wrote: > A Xen HVM guest running with KASLR enabled will die rather soon today > due to the shared info page mapping is using va() too early. This was As a minor grammar issue, either s/due to/because/ or s/mapping is using/mapping using/ ~Andrew > introduced by

Re: [Xen-devel] [PATCH v2 3/3] xen: fix hvm guest with kaslr enabled

2017-08-08 Thread Andrew Cooper
On 28/07/17 11:23, Juergen Gross wrote: > A Xen HVM guest running with KASLR enabled will die rather soon today > due to the shared info page mapping is using va() too early. This was As a minor grammar issue, either s/due to/because/ or s/mapping is using/mapping using/ ~Andrew > introduced by

[PATCH v2 3/3] xen: fix hvm guest with kaslr enabled

2017-07-28 Thread Juergen Gross
A Xen HVM guest running with KASLR enabled will die rather soon today due to the shared info page mapping is using va() too early. This was introduced by commit a5d5f328b0e2baa5ee7c119fd66324eb79eeeb66 ("xen: allocate page for shared info page from low memory"). In order to fix this use

[PATCH v2 3/3] xen: fix hvm guest with kaslr enabled

2017-07-28 Thread Juergen Gross
A Xen HVM guest running with KASLR enabled will die rather soon today due to the shared info page mapping is using va() too early. This was introduced by commit a5d5f328b0e2baa5ee7c119fd66324eb79eeeb66 ("xen: allocate page for shared info page from low memory"). In order to fix this use