From: Alexander Graf <agraf@suse.de>
To: Thomas Huth <huth@tuxfamily.org>, Philipp Kern <phil@philkern.de>,
qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] target-s390x: Mask the SIGP order_code to 8bit.
Date: Wed, 26 Aug 2015 11:18:42 +0200 [thread overview]
Message-ID: <55DD8472.4050600@suse.de> (raw)
In-Reply-To: <55D60B51.1000201@tuxfamily.org>
On 20.08.15 19:16, Thomas Huth wrote:
> On 18/08/15 04:50, Philipp Kern wrote:
>> According to "CPU Signaling and Response", "Signal-Processor Orders",
>> the order field is bit position 56-63. Without this, the Linux
>> guest kernel is sometimes unable to stop emulation and enters
>> an infinite loop of "XXX unknown sigp: 0xffffffff00000005".
>>
>> Signed-off-by: Philipp Kern <phil@philkern.de>
>> ---
>> target-s390x/misc_helper.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/target-s390x/misc_helper.c b/target-s390x/misc_helper.c
>> index 8eac0e1..0f0907c 100644
>> --- a/target-s390x/misc_helper.c
>> +++ b/target-s390x/misc_helper.c
>> @@ -500,7 +500,7 @@ uint32_t HELPER(sigp)(CPUS390XState *env, uint64_t order_code, uint32_t r1,
>> /* Remember: Use "R1 or R1 + 1, whichever is the odd-numbered register"
>> as parameter (input). Status (output) is always R1. */
>>
>> - switch (order_code) {
>> + switch (order_code & 0xff) {
>> case SIGP_SET_ARCH:
>> /* switch arch */
>> break;
>
> Reviewed-by: Thomas Huth <thuth@tuxfamily.org>
Thanks, applied to s390-next.
Alex
next prev parent reply other threads:[~2015-08-26 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1439897731-3645-1-git-send-email-phil@philkern.de>
2015-08-18 11:50 ` [Qemu-devel] [PATCH] target-s390x: Mask the SIGP order_code to 8bit Philipp Kern
2015-08-20 17:16 ` Thomas Huth
2015-08-26 9:18 ` Alexander Graf [this message]
2016-05-29 14:10 ` Philipp Kern
2017-04-23 22:32 Aurelien Jarno
2017-04-24 8:25 ` Alexander Graf
2017-04-25 9:51 ` Richard Henderson
2017-04-25 11:21 ` Philipp Kern
2017-04-25 11:32 ` Alexander Graf
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=55DD8472.4050600@suse.de \
--to=agraf@suse.de \
--cc=huth@tuxfamily.org \
--cc=phil@philkern.de \
--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).