On 28/06/2016 17:42, Peter Maydell wrote:
> Ping for review?
The patch is trivial, the hard part was coming up with the message for
the user. :) Go ahead!
Paolo
> thanks
> -- PMM
>
> On 20 June 2016 at 18:07, Peter Maydell wrote:
>> In get_page_addr_code(), if the
On 28 June 2016 at 18:49, Paolo Bonzini wrote:
> On 28/06/2016 17:42, Peter Maydell wrote:
>> Ping for review?
>
> The patch is trivial, the hard part was coming up with the message for
> the user. :)
Sure, but review includes whether the message makes sense :-)
> Go ahead!
On 06/20/2016 10:07 AM, Peter Maydell wrote:
In get_page_addr_code(), if the guest program counter turns out not to
be in ROM or RAM, we can't handle executing from it, and we call
cpu_abort(). This results in the message
qemu: fatal: Trying to execute code outside RAM or ROM at 0x0800
Ping for review?
thanks
-- PMM
On 20 June 2016 at 18:07, Peter Maydell wrote:
> In get_page_addr_code(), if the guest program counter turns out not to
> be in ROM or RAM, we can't handle executing from it, and we call
> cpu_abort(). This results in the message
>
On 20 June 2016 at 20:16, Mark Cave-Ayland
wrote:
> Excellent! Another use case I see here is with HelenOS/ppc whose
> bootloader is fixed at address 0x800 (128Mb) and so if you don't
> increase the memory above the default then you end up with this panic,
>
On 20/06/16 18:07, Peter Maydell wrote:
> In get_page_addr_code(), if the guest program counter turns out not to
> be in ROM or RAM, we can't handle executing from it, and we call
> cpu_abort(). This results in the message
> qemu: fatal: Trying to execute code outside RAM or ROM at 0x0800
>
In get_page_addr_code(), if the guest program counter turns out not to
be in ROM or RAM, we can't handle executing from it, and we call
cpu_abort(). This results in the message
qemu: fatal: Trying to execute code outside RAM or ROM at 0x0800
followed by a guest register dump, and then QEMU