From: Thomas Huth <thuth@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>, qemu-devel@nongnu.org
Cc: rth@twiddle.net, agraf@suse.de, borntraeger@de.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2 3/3] s390x: wire up diag288 in tcg
Date: Fri, 18 Aug 2017 13:52:28 +0200 [thread overview]
Message-ID: <2d380a07-4298-e1a7-7151-dec1380c8f39@redhat.com> (raw)
In-Reply-To: <20170818114844.30061-4-cohuck@redhat.com>
On 18.08.2017 13:48, Cornelia Huck wrote:
> Make the diag288 watchdog useable via tcg as well.
>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
> target/s390x/misc_helper.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/target/s390x/misc_helper.c b/target/s390x/misc_helper.c
> index 5a1eba02ab..34d730ba73 100644
> --- a/target/s390x/misc_helper.c
> +++ b/target/s390x/misc_helper.c
> @@ -103,6 +103,10 @@ void HELPER(diag)(CPUS390XState *env, uint32_t r1, uint32_t r3, uint32_t num)
> handle_diag_308(env, r1, r3);
> r = 0;
> break;
> + case 0x288:
> + /* time bomb (watchdog) */
> + r = handle_diag_288(env, r1, r3);
> + break;
> default:
> r = -1;
> break;
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2017-08-18 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 11:48 [Qemu-devel] [PATCH v2 0/3] s390x: diag-related things Cornelia Huck
2017-08-18 11:48 ` [Qemu-devel] [PATCH v2 1/3] s390x/tcg: specification exception for unknown diag Cornelia Huck
2017-08-18 11:51 ` Thomas Huth
2017-08-18 11:48 ` [Qemu-devel] [PATCH v2 2/3] watchdog/wdt_diag288: Mark diag288 watchdog as non-hotpluggable Cornelia Huck
2017-08-18 14:51 ` David Hildenbrand
2017-08-18 11:48 ` [Qemu-devel] [PATCH v2 3/3] s390x: wire up diag288 in tcg Cornelia Huck
2017-08-18 11:52 ` Thomas Huth [this message]
2017-08-21 15:07 ` [Qemu-devel] [PATCH v2 0/3] s390x: diag-related things 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=2d380a07-4298-e1a7-7151-dec1380c8f39@redhat.com \
--to=thuth@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=qemu-devel@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).