From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Boettcher <alexander.boettcher@genode-labs.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, rth@twiddle.net,
"fred konrad" <fred.konrad@greensocs.com>,
"crosthwaite peter" <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] Qemu deadlocks in tb_lock when using SVM+SoftMMU
Date: Mon, 6 Mar 2017 15:56:35 -0500 (EST) [thread overview]
Message-ID: <1394881299.29178732.1488833795531.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <986fbee4-e620-802d-b985-f732768ad039@genode-labs.com>
----- Original Message -----
> From: "Alexander Boettcher" <alexander.boettcher@genode-labs.com>
> To: "Alex Bennée" <alex.bennee@linaro.org>
> Cc: qemu-devel@nongnu.org, rth@twiddle.net, "fred konrad" <fred.konrad@greensocs.com>, pbonzini@redhat.com,
> "crosthwaite peter" <crosthwaite.peter@gmail.com>
> Sent: Monday, March 6, 2017 9:11:04 PM
> Subject: Re: Qemu deadlocks in tb_lock when using SVM+SoftMMU
>
> Hello,
>
> thank you for your effort.
>
> With your patch I get now a 0x3f exception shown by the hypervisor,
> which I have never encountered so far before. The guest kernel seems not
> to start, at least no life sign is shown.
>
> For me the patch of Paolo Bonzini works reliable.
Let's use mine then. :) I'll post it properly tomorrow.
Paolo
> How to proceed ?
>
> Thanks,
>
> Alex.
>
> On 06.03.2017 17:24, Alex Bennée wrote:
> >
> > 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
> >
>
> --
> Alexander Boettcher
> Genode Labs
>
> http://www.genode-labs.com - http://www.genode.org
>
> Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden
> Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth
>
prev parent reply other threads:[~2017-03-06 20:56 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 ` [Qemu-devel] Qemu deadlocks in tb_lock when using SVM+SoftMMU Alex Bennée
2017-03-06 20:11 ` Alexander Boettcher
2017-03-06 20:56 ` Paolo Bonzini [this message]
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=1394881299.29178732.1488833795531.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alexander.boettcher@genode-labs.com \
--cc=crosthwaite.peter@gmail.com \
--cc=fred.konrad@greensocs.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).