From: Wayne Li <waynli329@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject:
Date: Wed, 19 Feb 2020 23:40:10 -0600 [thread overview]
Message-ID: <CAM2K0npCdHfCeMCKO9TX_ifQGDZFFNyMEKH2qByYL9SnXnaPmw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
Dear QEMU list members,
This will kind of be a repost but I'd like to post my question again
because I've gained some more knowledge that makes me feel that my question
would be easier to answer. So we developed a custom-made QEMU VM that
emulates a custom machine that has an e5500 processor. I'm running this VM
on a T4240-RDB board which has an e6500 processor and I'm trying to get the
VM running with KVM enabled. The problem I'm having is the program counter
refuses to increment at all. It just stays at the address 0xFFFFFFFC. On
a run without KVM enabled, the VM will also start executing at this same
address but the program counter beings to increment immediately. I know
this is a custom QEMU VM and maybe some of the startup stuff we do could be
causing problems, but what could possibly stop the program counter from
incrementing altogether?
Also, I do have another side question. When running with KVM enabled, I
see the kernel-level ioctl call KVM_RUN running and then returning over and
over again (by the way before the VM kinda grinds to a halt I only see QEMU
make the KVM_RUN call twice, but the kernel-level ioctl function is being
called over and over again for some reason). And each time the KVM_RUN
call returns, the return-from-interrupt takes the VM to the address
0xFFFFFFFC. What is the KVM_RUN ioctl call used for? Why is it being
called over and over again? Maybe if I understood this better I'd be able
to figure out what's stopping my program counter from incrementing.
-Thanks, Wayne Li
[-- Attachment #2: Type: text/html, Size: 1669 bytes --]
next reply other threads:[~2020-02-20 5:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 5:40 Wayne Li [this message]
2020-02-20 8:44 ` Program counter stuck at 0xFFFFFFFC when emulating e5500 processor on T4240-RDB board Philippe Mathieu-Daudé
2020-03-11 5:03 ` David Gibson
2020-02-20 9:57 ` Peter Maydell
2020-02-20 16:52 ` Re: Wayne Li
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=CAM2K0npCdHfCeMCKO9TX_ifQGDZFFNyMEKH2qByYL9SnXnaPmw@mail.gmail.com \
--to=waynli329@gmail.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).