From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Pranith Kumar <bobby.prani@gmail.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Richard Henderson <rth@twiddle.net>,
"open list:Overall" <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] tcg: handle EXCP_ATOMIC exception properly
Date: Fri, 10 Feb 2017 14:37:38 +0000 [thread overview]
Message-ID: <87vasiw1ql.fsf@linaro.org> (raw)
In-Reply-To: <3f702266-1ac2-57c5-e0f8-3dec07b450d2@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 10/02/2017 13:33, Alex Bennée wrote:
>> That said for TCG system emulation EXCP_ATOMIC is currently broken with
>> respect to debugging. However for the initial guests/host combination of
>> ARMv7/8 on x86_64 we don't need the fallback with pretty much 99% of
>> deployed hosts. How about the following:
>>
>> - drop Pranith's patch for the current MTTCG series
>> - replace with an error/abort on EXCP_ATOMIC
>
> Don't even replace it? :)
I guess - the failure mode is only when we single step? Should we not
try to emit a warning like we do for the mismatched MOs?
>
> Paolo
>
>> - proceed with merge as plan
>> - tackle the BQL lock next (along with more MTTCG guest/targets enablement)
--
Alex Bennée
next prev parent reply other threads:[~2017-02-10 14:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 1:45 [Qemu-devel] [PATCH] tcg: handle EXCP_ATOMIC exception properly Pranith Kumar
2017-02-10 4:54 ` Pranith Kumar
2017-02-10 11:34 ` Paolo Bonzini
2017-02-10 12:18 ` Alex Bennée
2017-02-10 12:29 ` Paolo Bonzini
2017-02-10 12:57 ` Alex Bennée
2017-02-10 13:59 ` Pranith Kumar
2017-02-10 12:13 ` Alex Bennée
2017-02-10 12:15 ` Paolo Bonzini
2017-02-10 12:33 ` Alex Bennée
2017-02-10 13:12 ` Paolo Bonzini
2017-02-10 14:37 ` Alex Bennée [this message]
2017-02-10 14:44 ` 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=87vasiw1ql.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=bobby.prani@gmail.com \
--cc=crosthwaite.peter@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).