From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Aurelien Jarno <aurelien@aurel32.net>
Cc: "open list:All patches CC here" <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PULL 2/5] target/sh4: fix reset when using a kernel and an initrd
Date: Tue, 30 May 2017 10:02:54 -0500 [thread overview]
Message-ID: <dc4c904d-c794-fd9f-66ec-141861cf0a33@redhat.com> (raw)
In-Reply-To: <20170530101746.GA25884@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
On 05/30/2017 05:17 AM, Stefan Hajnoczi wrote:
> On Mon, May 29, 2017 at 09:30:13PM +0200, Aurelien Jarno wrote:
>> When a masked exception happens, the SH4 CPU generates a non-masked
>> reset exception, which then jumps to the reset vector at address
>> 0xA0000000. While this is emulated correctly in QEMU, this does not
>> work when using a kernel and initrd as this address then contain an
>> illegal instruction (and there is no guarantee the kernel and initrd
>> haven't been overwritten).
>>
>> + qemu_system_reset_request();
>> + return;
>
> The qemu_system_reset_request() prototype is changing. There is a
> conflict with another merged pull request. Please rebase onto
> https://github.com/stefanha/qemu.git staging.
>
> target/sh4/helper.c:102:39: error: too few arguments to function call, single argument 'reason' was not specified
> qemu_system_reset_request();
> ~~~~~~~~~~~~~~~~~~~~~~~~~ ^
You'll probably want SHUTDOWN_CAUSE_GUEST_RESET as the reason, based on
the changes made to other target/ files.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-05-30 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170529193016.6888-1-aurelien@aurel32.net>
2017-05-29 19:30 ` [Qemu-devel] [PULL 1/5] target/sh4: log unauthorized accesses using qemu_log_mask Aurelien Jarno
2017-05-30 9:52 ` Stefan Hajnoczi
2017-05-30 11:12 ` Aurelien Jarno
2017-05-30 10:18 ` Stefan Hajnoczi
2017-05-30 11:12 ` Aurelien Jarno
2017-05-29 19:30 ` [Qemu-devel] [PULL 2/5] target/sh4: fix reset when using a kernel and an initrd Aurelien Jarno
2017-05-30 10:17 ` Stefan Hajnoczi
2017-05-30 15:02 ` Eric Blake [this message]
2017-05-30 16:21 ` Aurelien Jarno
2017-05-29 19:30 ` [Qemu-devel] [PULL 3/5] target/sh4: introduce DELAY_SLOT_MASK Aurelien Jarno
2017-05-29 19:30 ` [Qemu-devel] [PULL 4/5] target/sh4: ignore interrupts in a delay slot Aurelien Jarno
2017-05-29 19:30 ` [Qemu-devel] [PULL 5/5] target/sh4: fix RTE instruction " Aurelien Jarno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc4c904d-c794-fd9f-66ec-141861cf0a33@redhat.com \
--to=eblake@redhat.com \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).