From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel <qemu-devel@nongnu.org>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] target-ppc: gdbstub breakpoints get stuck in an infinite loop on next/continue
Date: Sat, 22 Oct 2016 09:02:45 +1100 [thread overview]
Message-ID: <1477087365.2430.3.camel@kernel.crashing.org> (raw)
In-Reply-To: <7e2d79de-5e4b-6140-63e1-f6829d834b4a@ilande.co.uk>
On Fri, 2016-10-21 at 15:18 +0100, Mark Cave-Ayland wrote:
>
> bd6fefe71cec5a0c7d2be4ac96307f25db56abf9 is the first bad commit
> commit bd6fefe71cec5a0c7d2be4ac96307f25db56abf9
> Author: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Date: Wed Jul 27 16:56:32 2016 +1000
>
> ppc: Make tlb_fill() use new exception helper
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
>
> :040000 040000 3494b2d68eef71c8f7c7d4e57c5ff715146028b2
> 00849bf5889d8ee5b5ce633122b7aedf4a734372 M linux-user
> :040000 040000 32b1a8078a44c44e6bfd2184061b6da553cfc821
> 58afefec7a9fc5380fb408758a11dbe749010b97 M target-ppc
Hrm, that patch does a lot more that the subject (and lack of cset
comment) implies. I wonder if it got some rebase damage here.
In the meantime, look at 24a2d2ac2cfbb699cab216aaf118c8503f22817c
" ppc: Fix single step with gdb stub" in my wip branch, see if that
helps.
next prev parent reply other threads:[~2016-10-21 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 14:18 [Qemu-devel] target-ppc: gdbstub breakpoints get stuck in an infinite loop on next/continue Mark Cave-Ayland
2016-10-21 22:02 ` Benjamin Herrenschmidt [this message]
2016-10-22 8:22 ` Mark Cave-Ayland
2016-10-24 1:00 ` David Gibson
2016-10-24 20:08 ` Benjamin Herrenschmidt
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=1477087365.2430.3.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).