Comment 5 for bug 2058466

@Paolo thanks for probing this. I finally managed to get my hands on a suitable power system with recent enough kernel to reproduce this and file an upstream bug report, and the conversation there led me to conclude that it's just a faulty assumption in the test (namely that the initial allocation code would need to allocate a new page, which isn't the case when the page size is 64k).

I'll just XFAIL this on power for now, and mark this a low priority on the upstream bug tracker (as I'd like the test to be fixed)