From: "Alex Bennée" <alex.bennee@linaro.org>
To: Alexander Boettcher <alexander.boettcher@genode-labs.com>
Cc: qemu-devel@nongnu.org, rth@twiddle.net,
fred.konrad@greensocs.com, pbonzini@redhat.com,
crosthwaite.peter@gmail.com
Subject: Re: [Qemu-devel] Qemu deadlocks in tb_lock when using SVM+SoftMMU
Date: Mon, 06 Mar 2017 16:24:37 +0000 [thread overview]
Message-ID: <87h936ida2.fsf@linaro.org> (raw)
In-Reply-To: <d208c3f0-2e57-0b54-f18f-b5e27d698e28@genode-labs.com>
Alexander Boettcher <alexander.boettcher@genode-labs.com> writes:
> Hi,
<snip>
>
> Sometimes Qemu just succeeds if the timing is well, will see.
>
> But this is not the point of this issue atm.
I've sent a patch that works as Richard suggested. However your test
image seems to run into other issues. I have tested it on my known good
x86 image and it works.
However my knowledge of x86's interrupt architecture is fairly minimal
so I'm looking for testing/feedback on the patch.
>
> Alex.
--
Alex Bennée
next prev parent reply other threads:[~2017-03-06 16:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 16:59 [Qemu-devel] Qemu deadlocks in tb_lock when using SVM+SoftMMU Alexander Boettcher
2017-03-05 21:32 ` Alex Bennée
2017-03-06 1:34 ` Richard Henderson
2017-03-06 16:58 ` Paolo Bonzini
2017-03-06 19:21 ` Richard Henderson
2017-03-06 20:03 ` Alexander Boettcher
2017-03-06 13:15 ` Alex Bennée
2017-03-06 13:21 ` Alexander Boettcher
2017-03-06 14:42 ` Alex Bennée
2017-03-06 15:11 ` Alexander Boettcher
2017-03-06 15:57 ` [Qemu-devel] [PATCH] target/i386: move nested exception check to x86_cpu_exec_interrupt Alex Bennée
2017-03-06 19:24 ` Richard Henderson
2017-03-07 15:03 ` Alex Bennée
2017-03-06 16:24 ` Alex Bennée [this message]
2017-03-06 20:11 ` [Qemu-devel] Qemu deadlocks in tb_lock when using SVM+SoftMMU Alexander Boettcher
2017-03-06 20:56 ` Paolo Bonzini
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=87h936ida2.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=alexander.boettcher@genode-labs.com \
--cc=crosthwaite.peter@gmail.com \
--cc=fred.konrad@greensocs.com \
--cc=pbonzini@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).