All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Fedorov <serge.fdrv@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] target-arm: Fix non-CPU breakpoint handling in arm_debug_excp_handler()
Date: Fri, 6 Nov 2015 15:23:19 +0300	[thread overview]
Message-ID: <563C9BB7.9080404@gmail.com> (raw)
In-Reply-To: <CAFEAcA8pcbt32sowe929VqeYbDqwFq1U3HQUS1F4OKXyAEFExA@mail.gmail.com>

On 06.11.2015 14:57, Peter Maydell wrote:
> On 5 November 2015 at 12:26, Sergey Fedorov <serge.fdrv@gmail.com> wrote:
>> Do not raise a CPU exception if no CPU breakpoint has fired, since
>> singlestep is also done by generating a debug internal exception. This
>> fixes a bug with singlestepping in gdbstub.
>>
>> Signed-off-by: Sergey Fedorov <serge.fdrv@gmail.com>
>> ---
>> This is a v2 of 'target-arm: Fix arm_debug_excp_handler() for singlestep
>> enabled.'
>>
>> Changes in v2:
>>  * Commit subject and body changed
>>  * Instead of checking for singlestep enabled, CPU breakpoint match checked
> Isn't this fixing singlestep, not non-CPU breakpoints?
> (GDB breakpoints were already being checked for and early-returned.)

Sorry for the confusing commit subject, actually, I meant "fix handling
of EXCP_DEBUG in case of no CPU breakpoint fired" :)

>
> I'll tweak the commit subject line and apply to target-arm.next.
>
> Incidentally, this only affects gdbstub singlestep for aarch64
> in practice, because gdb for 32-bit ARM uses set-breakpoint-and-continue
> rather than the singlestep gdbstub protocol command.
>
>>  target-arm/op_helper.c | 8 +++++++-
>>  1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/target-arm/op_helper.c b/target-arm/op_helper.c
>> index b5db345..6cd54c8 100644
>> --- a/target-arm/op_helper.c
>> +++ b/target-arm/op_helper.c
>> @@ -917,7 +917,13 @@ void arm_debug_excp_handler(CPUState *cs)
>>          uint64_t pc = is_a64(env) ? env->pc : env->regs[15];
>>          bool same_el = (arm_debug_target_el(env) == arm_current_el(env));
>>
>> -        if (cpu_breakpoint_test(cs, pc, BP_GDB)) {
>> +        /* (1) GDB breakpoints should be handled first.
>> +         * (2) Do not raise a CPU exception if no CPU breakpoint has fired,
>> +         * since singlestep is also done by generating a debug internal
>> +         * exception.
>> +         */
>> +        if (cpu_breakpoint_test(cs, pc, BP_GDB)
>> +            || !cpu_breakpoint_test(cs, pc, BP_CPU)) {
>>              return;
>>          }
>>
>> --
>> 1.9.1
>>
>

Thanks,
Sergey

      reply	other threads:[~2015-11-06 12:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05 12:26 [Qemu-devel] [PATCH v2] target-arm: Fix non-CPU breakpoint handling in arm_debug_excp_handler() Sergey Fedorov
2015-11-06 11:57 ` Peter Maydell
2015-11-06 12:23   ` Sergey Fedorov [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=563C9BB7.9080404@gmail.com \
    --to=serge.fdrv@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.