From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
Omair Javaid <omair.javaid@linaro.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v1 1/4] target/arm64: properly handle DBGVR RESS bits
Date: Thu, 01 Nov 2018 12:35:24 +0000 [thread overview]
Message-ID: <87va5h562b.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA9CDX02Mmt-i+2Ct=at_iS8pjcbSN+ZPhj+BYUC1xXrUQ@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On 26 September 2018 at 12:20, Alex Bennée <alex.bennee@linaro.org> wrote:
>> This only fails with some (broken) versions of gdb but we should
>> treat the top bits of DBGBVR as RESS. As the hardware may have IMPDEF
>> approaches to writes to this register we apply the sign extension when
>> checking breakpoints.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> ---
>> target/arm/kvm64.c | 12 +++++++++++-
>> 1 file changed, 11 insertions(+), 1 deletion(-)
>>
>> diff --git a/target/arm/kvm64.c b/target/arm/kvm64.c
>> index e0b8246283..80ad07ed0c 100644
>> --- a/target/arm/kvm64.c
>> +++ b/target/arm/kvm64.c
>> @@ -356,13 +356,23 @@ bool kvm_arm_hw_debug_active(CPUState *cs)
>> return ((cur_hw_wps > 0) || (cur_hw_bps > 0));
>> }
>>
>> +/*
>> + * We shouldn't rely on gdb correctly setting the top bits of DBGBVR
>> + * and the HW lists the top bits a RESS - sign-extending the top bit
>> + * of the VA address. As it is IMPDEF if the write is either a sign
>> + * extension or kept as is we might fix it up before we compare with
>> + * the correctly reported and sign extended address.
>> + */
>> +
>> static bool find_hw_breakpoint(CPUState *cpu, target_ulong pc)
>> {
>> int i;
>>
>> for (i = 0; i < cur_hw_bps; i++) {
>> HWBreakpoint *bp = get_hw_bp(i);
>> - if (bp->bvr == pc) {
>> + target_ulong bvr = bp->bvr;
>> + bvr |= extract64(bvr, 52, 1) ? MAKE_64BIT_MASK(53, 11) : 0;
>> + if (bvr == pc) {
>> return true;
>> }
>> }
>
> Shouldn't we be sanitizing the addresses we get from gdb
> before we put them into the hardware watchpoint registers,
> rather than doing the sign extension when we read the registers?
I guess that works too. I'll switch it around.
--
Alex Bennée
next prev parent reply other threads:[~2018-11-01 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180926112048.17778-1-alex.bennee@linaro.org>
[not found] ` <20180926112048.17778-2-alex.bennee@linaro.org>
2018-10-02 9:54 ` [Qemu-devel] [PATCH v1 1/4] target/arm64: properly handle DBGVR RESS bits Peter Maydell
2018-11-01 12:35 ` Alex Bennée [this message]
[not found] ` <20180926112048.17778-3-alex.bennee@linaro.org>
2018-10-02 9:55 ` [Qemu-devel] [PATCH v1 2/4] target/arm64: hold BQL when calling do_interrupt() Peter Maydell
[not found] ` <20180926112048.17778-4-alex.bennee@linaro.org>
2018-10-02 9:56 ` [Qemu-devel] [PATCH v1 3/4] target/arm64: kvm debug set target_el when passing exception to guest Peter Maydell
[not found] ` <20180926112048.17778-5-alex.bennee@linaro.org>
2018-10-02 9:59 ` [Qemu-devel] [PATCH v1 4/4] tests/guest-debug: fix scoping of failcount Peter Maydell
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=87va5h562b.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=omair.javaid@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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 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).