From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: Richard Henderson <richard.henderson@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [BUG] nanoMIPS support problem related to extract2 support for i386 TCG target
Date: Fri, 12 Jul 2019 20:09:40 +0200 [thread overview]
Message-ID: <CAL1e-=ixrEhBeakGDW8xJVBBzRkZTR4d69w38HHmvxVUzOCkSw@mail.gmail.com> (raw)
Hello, Richard, Peter, and others.
As a part of activities before 4.1 release, I tested nanoMIPS support
in QEMU (which was officially fully integrated in 4.0, is currently
limited to system mode only, and was tested in a similar fashion right
prior to 4.0).
This support appears to be broken now. Following command line works in
4.0, but results in kernel panic for the current tip of the tree:
~/Build/qemu-test-revert-c6fb8c0cf704/mipsel-softmmu/qemu-system-mipsel
-cpu I7200 -kernel generic_nano32r6el_page4k -M malta -serial stdio -m
1G -hda nanomips32r6_le_sf_2017.05-03-59-gf5595d6.ext4 -append
"mem=256m@0x0 rw console=ttyS0 vga=cirrus vesa=0x111 root=/dev/sda"
(kernel and rootfs image files used in this commend line can be
downloaded from the locations mentioned in our user guide)
The quick bisect points to the commit:
commit c6fb8c0cf704c4a1a48c3e99e995ad4c58150dab
Author: Richard Henderson <richard.henderson@linaro.org>
Date: Mon Feb 25 11:42:35 2019 -0800
tcg/i386: Support INDEX_op_extract2_{i32,i64}
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
Please advise on further actions.
Yours,
Aleksandar
next reply other threads:[~2019-07-12 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 18:09 Aleksandar Markovic [this message]
2019-07-12 18:19 ` [Qemu-devel] [BUG] nanoMIPS support problem related to extract2 support for i386 TCG target Aleksandar Markovic
2019-07-12 19:07 ` Aleksandar Markovic
2019-07-13 7:21 ` Alex Bennée
2019-07-15 19:48 ` Aleksandar Markovic
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='CAL1e-=ixrEhBeakGDW8xJVBBzRkZTR4d69w38HHmvxVUzOCkSw@mail.gmail.com' \
--to=aleksandar.m.mail@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).