From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Fix ptrace software breakpoints
Date: Tue, 20 Jul 2010 18:23:33 +0100 [thread overview]
Message-ID: <000c01cb2830$47f8a590$d7e9f0b0$@deacon@arm.com> (raw)
In-Reply-To: <FB3C047B-0B6C-4605-A481-667C7E75B745@ti.com>
Hi Rob,
> fyi, my gdb test (git://github.com/robclark/gdb-test.git) seems to be passing reliable so far (I
> haven't seen it fail once yet) with these patches.. without these patches, it was triggering passing
> the breakpoing 90+% of the time.
>
> I'll keep you posted if I notice any issues, but so far so good!
Does this mean you haven't seen it fail yet :)? If so, any
chance I could have a tested-by please?
Will
next prev parent reply other threads:[~2010-07-20 17:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 15:53 [PATCH 0/2] Fix ptrace software breakpoints Will Deacon
2010-07-15 15:53 ` [PATCH 1/2] ARM: errata: TLBIASIDIS and TLBIMVAIS operations can broadcast a faulty ASID Will Deacon
2010-07-15 15:53 ` [PATCH 2/2] ARM: flush_ptrace_access: invalidate all I-caches Will Deacon
2010-07-15 16:32 ` Russell King - ARM Linux
2010-07-15 16:43 ` Will Deacon
2010-07-15 16:54 ` Catalin Marinas
2010-07-19 16:23 ` Will Deacon
2010-08-04 11:24 ` Will Deacon
2010-07-15 16:21 ` [PATCH 1/2] ARM: errata: TLBIASIDIS and TLBIMVAIS operations can broadcast a faulty ASID Shilimkar, Santosh
2010-07-15 16:32 ` Will Deacon
2010-07-15 16:43 ` Shilimkar, Santosh
2010-07-16 4:15 ` [PATCH 0/2] Fix ptrace software breakpoints Rob Clark
2010-07-20 17:23 ` Will Deacon [this message]
2010-07-27 1:30 ` Rob Clark
2010-07-27 9:43 ` Will Deacon
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='000c01cb2830$47f8a590$d7e9f0b0$@deacon@arm.com' \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).