From: Giovanni Mascellani <gio@debian.org>
To: Cornelia Huck <cohuck@redhat.com>, David Hildenbrand <david@redhat.com>
Cc: Bug 1815024 <1815024@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1815024] [NEW] SIGILL on instruction "stck" under qemu-s390x in user mode
Date: Thu, 7 Feb 2019 12:05:09 +0100 [thread overview]
Message-ID: <6c5ac94e-065f-e66a-2df2-5d8ac81c76e1@debian.org> (raw)
In-Reply-To: <20190207114913.2c5f2c5b.cohuck@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
Hi, thanks for answering!
Il 07/02/19 11:49, Cornelia Huck ha scritto:
> Did that work before commit 7de3b1cdc67 ("s390x/tcg: properly implement
> the TOD")?
It does not seem so:
$ /qemu-s390x-new -version
qemu-s390x version 2.12.50 (v2.12.0-1983-g7de3b1cdc6-dirty)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
$ /qemu-s390x-new ./a.out
Istruzione non consentita
(i.e., "illegal instruction")
But this might be expected. Now I go to the previous commit (f777b20544)
and recompile:
$ /qemu-s390x-new -version
qemu-s390x version 2.12.50 (v2.12.0-1982-gf777b20544-dirty)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
$ /qemu-s390x-new ./a.out
Istruzione non consentita
So again. And even going back to 76ed4b18de (i.e., skipping a few
apparently related s390x commits):
$ /qemu-s390x-new -version
qemu-s390x version 2.12.50 (v2.12.0-1976-g76ed4b18de-dirty)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
$ /qemu-s390x-new ./a.out
Istruzione non consentita
> stckf will end up at the same helper, so it seems likely to hit the
> same problem.
I guessed so.
Thanks again, Giovanni.
--
Giovanni Mascellani <g.mascellani@gmail.com>
Postdoc researcher - Université Libre de Bruxelles
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-02-07 11:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 9:46 [Qemu-devel] [Bug 1815024] [NEW] SIGILL on instruction "stck" under qemu-s390x in user mode Giovanni Mascellani
2019-02-07 9:46 ` [Qemu-devel] [Bug 1815024] " Giovanni Mascellani
2019-02-07 9:46 ` Giovanni Mascellani
2019-02-07 9:48 ` Giovanni Mascellani
2019-02-07 10:49 ` [Qemu-devel] [Bug 1815024] [NEW] " Cornelia Huck
2019-02-07 11:05 ` Giovanni Mascellani [this message]
2019-02-07 11:26 ` Thomas Huth
2019-02-07 11:46 ` Giovanni Mascellani
2019-02-07 12:01 ` Thomas Huth
2019-02-07 12:15 ` Richard Henderson
2019-02-07 12:36 ` Thomas Huth
2019-02-07 13:05 ` Richard Henderson
2019-02-07 13:00 ` Giovanni Mascellani
2019-02-07 13:09 ` Thomas Huth
2019-02-22 15:24 ` [Qemu-devel] [Bug 1815024] " Thomas Huth
2019-04-24 6:09 ` Thomas Huth
2019-04-24 6:09 ` Thomas Huth
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=6c5ac94e-065f-e66a-2df2-5d8ac81c76e1@debian.org \
--to=gio@debian.org \
--cc=1815024@bugs.launchpad.net \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).