From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>,
Richard Henderson <rth@twiddle.net>,
David Hildenbrand <david@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
Janosch Frank <frankja@linux.ibm.com>
Subject: Re: [PATCH] s390x/tcg: clear local interrupts on reset normal
Date: Thu, 5 Dec 2019 11:56:33 +0100 [thread overview]
Message-ID: <9e887988-652d-d325-3524-df5f3de5ce08@redhat.com> (raw)
In-Reply-To: <20191205103844.10404-1-cohuck@redhat.com>
Hi Cornelia,
On 12/5/19 11:38 AM, Cornelia Huck wrote:
> We neglected to clean up pending interrupts and emergency signals;
> fix that.
>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
>
> Noted while looking at the fixes for the kvm reset handling.
IIUC we always neglected to clean these fields, but Janosh recent work
[*] helped you to realize that?
[*] https://www.mail-archive.com/qemu-devel@nongnu.org/msg661541.html
> We now clear some fields twice in the paths for clear or initial reset;
> but (a) we already do that for other fields and (b) it does not really
> hurt. Maybe we should give the cpu structure some love in the future,
> as it's not always clear whether some fields are tcg only.
>
> ---
> target/s390x/cpu.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/target/s390x/cpu.c b/target/s390x/cpu.c
> index 829ce6ad5491..f2572961dc3a 100644
> --- a/target/s390x/cpu.c
> +++ b/target/s390x/cpu.c
> @@ -133,6 +133,9 @@ static void s390_cpu_reset(CPUState *s, cpu_reset_type type)
> case S390_CPU_RESET_NORMAL:
> env->pfault_token = -1UL;
> env->bpbc = false;
> + env->pending_int = 0;
> + env->external_call_addr = 0;
> + bitmap_zero(env->emergency_signals, S390_MAX_CPUS);
> break;
> default:
> g_assert_not_reached();
>
next prev parent reply other threads:[~2019-12-05 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 10:38 [PATCH] s390x/tcg: clear local interrupts on reset normal Cornelia Huck
2019-12-05 10:56 ` Philippe Mathieu-Daudé [this message]
2019-12-05 11:02 ` Cornelia Huck
2019-12-06 9:36 ` David Hildenbrand
2019-12-06 10:27 ` Cornelia Huck
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=9e887988-652d-d325-3524-df5f3de5ce08@redhat.com \
--to=philmd@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
/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).