On 06/20/2016 06:25 AM, Peter Maydell wrote:
On 19 June 2016 at 19:24, Richard Henderson wrote:
On 06/19/2016 02:46 AM, Peter Maydell wrote:
This is supposed to work -- for instance the linux-user/mmap.c
code has support for host pages and target pages not being the same.
In
On 06/18/2016 06:15 PM, Timothy Pearson wrote:
> Attempting to use host pages larger than the guest leads to
> alignment errors during ELF load in the best case, and an
> initialization failure inside NPTL in the worst case, causing
> all fork() requests inside the guest to fail.
Long subject
On 19 June 2016 at 19:24, Richard Henderson wrote:
> On 06/19/2016 02:46 AM, Peter Maydell wrote:
>> This is supposed to work -- for instance the linux-user/mmap.c
>> code has support for host pages and target pages not being the same.
>> In particular for ARM guests
On 06/19/2016 02:46 AM, Peter Maydell wrote:
On 19 June 2016 at 01:11, Timothy Pearson
wrote:
Attempting to use host pages larger than the guest leads to
alignment errors during ELF load in the best case, and an
initialization failure inside NPTL in the worst
On 19 June 2016 at 01:11, Timothy Pearson
wrote:
> Attempting to use host pages larger than the guest leads to
> alignment errors during ELF load in the best case, and an
> initialization failure inside NPTL in the worst case, causing
> all fork() requests inside
Attempting to use host pages larger than the guest leads to
alignment errors during ELF load in the best case, and an
initialization failure inside NPTL in the worst case, causing
all fork() requests inside the guest to fail.
Warn when thread space cannot be set up, and suggest reducing
host page
Attempting to use host pages larger than the guest leads to
alignment errors during ELF load in the best case, and an
initialization failure inside NPTL in the worst case, causing
all fork() requests inside the guest to fail.
Warn when thread space cannot be set up, and suggest reducing
host page