From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Max Filippov" <jcmvbkbc@gmail.com>,
qemu-arm <qemu-arm@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH-for-5.0] gdbstub: Do not use memset() on GByteArray
Date: Tue, 14 Apr 2020 13:05:48 +0200 [thread overview]
Message-ID: <357e2335-b00f-cd28-4ade-d6286ace144f@redhat.com> (raw)
In-Reply-To: <CAFEAcA-PyMisjC25CSGyU5-ASjaAd7gQMabzMCR=uvudSBk-Fw@mail.gmail.com>
On 4/14/20 12:52 PM, Peter Maydell wrote:
> On Tue, 14 Apr 2020 at 11:24, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>>
>> Introduce gdb_get_zeroes() to fill a GByteArray with zeroes.
>>
>> Fixes: a010bdbe719 ("extend GByteArray to read register helpers")
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> ---
>> include/exec/gdbstub.h | 9 +++++++++
>> target/arm/gdbstub.c | 3 +--
>> target/xtensa/gdbstub.c | 6 ++----
>> 3 files changed, 12 insertions(+), 6 deletions(-)
>>
>> diff --git a/include/exec/gdbstub.h b/include/exec/gdbstub.h
>> index 30b909ebd2..b52d9933ee 100644
>> --- a/include/exec/gdbstub.h
>> +++ b/include/exec/gdbstub.h
>> @@ -125,6 +125,15 @@ static inline int gdb_get_reg128(GByteArray *buf, uint64_t val_hi,
>> return 16;
>> }
>>
>> +static inline int gdb_get_zeroes(GByteArray *array, size_t len)
>> +{
>> + for (size_t i = 0; i < len; i++) {
>> + gdb_get_reg8(array, '\0');
>> + }
>> +
>> + return len;
>> +}
>
> The other implementation option here would be
>
> guint oldlen = array->len;
> g_byte_array_set_size(array, oldlen + len);
> memset(array->data + oldlen, 0, len);
I thought about it but I'd rather not access GByteArray internals.
>
> For length values < 16 my guess is the perf difference is
> not going to be noticeable though.
On ARM it is called with size=12:
target/arm/gdbstub.c:50: memset(mem_buf, 0, 12);
On Xtensa it is only used with unimplemented registers:
qemu_log_mask(LOG_UNIMP, "%s from reg %d of unsupported type %d\n",
__func__, n, reg->type);
If you prefer I can use a static empty buffer of 16 bytes and copy from it:
static inline int gdb_get_zeroes(GByteArray *array, size_t len)
{
static const uint8_t zeroed_buf[16] = { };
g_byte_array_append(array, zeroed_buf, MIN(len, sizeof(zeroed_buf)));
for (size_t i = sizeof(zeroed_buf); i < len; i++) {
gdb_get_reg8(array, '\0');
}
return len;
}
>
> thanks
> -- PMM
>
next prev parent reply other threads:[~2020-04-14 11:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 10:24 [PATCH-for-5.0] gdbstub: Do not use memset() on GByteArray Philippe Mathieu-Daudé
2020-04-14 10:52 ` Peter Maydell
2020-04-14 11:05 ` Philippe Mathieu-Daudé [this message]
2020-04-14 11:49 ` Peter Maydell
2020-04-14 14:22 ` Alex Bennée
2020-04-14 16:09 ` Alex Bennée
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=357e2335-b00f-cd28-4ade-d6286ace144f@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=jcmvbkbc@gmail.com \
--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).