| commit | e568f9df086965813a318ff0558782ba90e59c33 | |
| author | Peter Maydell <peter.maydell@linaro.org> | |
| Tue, 3 Oct 2017 16:21:43 +0000 (3 17:21 +0100) | ||
| committer | Riku Voipio <riku.voipio@linaro.org> | |
| Mon, 16 Oct 2017 13:00:56 +0000 (16 16:00 +0300) | ||
| tree | 75b234d70163ab871e8f76f57a859fecdbe4d58b | treesnapshot (tar.gz zip) |
| parent | dd13df011d6e28beb16ef9e4548cd55fee84cb08 | commitdiff |
linux-user: Allow -R values up to 0xffff0000 for 32-bit ARM guests
The 32-bit ARM validate_guest_space() check tests whether the
specified -R value leaves enough space for us to put the
commpage in at 0xffff0f00. However it was incorrectly doing
a <= check for the check against (guest_base + guest_size),
which meant that it wasn't permitting the guest space to
butt right up against the commpage.
Fix the comparison, so that -R values all the way up to 0xffff0000
work correctly.
Reviewed-by: Emilio G. Cota <cota@braap.org>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
The 32-bit ARM validate_guest_space() check tests whether the
specified -R value leaves enough space for us to put the
commpage in at 0xffff0f00. However it was incorrectly doing
a <= check for the check against (guest_base + guest_size),
which meant that it wasn't permitting the guest space to
butt right up against the commpage.
Fix the comparison, so that -R values all the way up to 0xffff0000
work correctly.
Reviewed-by: Emilio G. Cota <cota@braap.org>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
| linux-user/elfload.c | diffblobblamehistory |