From: Joel Colledge <joel.colledge@linbit.com>
To: Leonard Crestez <leonard.crestez@nxp.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] scripts/gdb: fix lx-dmesg when CONFIG_PRINTK_CALLER is set
Date: Fri, 11 Oct 2019 15:01:55 +0200 [thread overview]
Message-ID: <CAGNP_+Wkya-wn-ckAmCoC0Mda=3cBDi4vYeZj-9SWT0EF8ja4w@mail.gmail.com> (raw)
In-Reply-To: <VI1PR04MB70239DA9EED5F689645071E9EE970@VI1PR04MB7023.eurprd04.prod.outlook.com>
On Fri, Oct 11, 2019 at 2:47 PM Leonard Crestez <leonard.crestez@nxp.com> wrote:
> This struct printk_log is quite small, I wonder if it's possible to do a
> single read for each log entry? This might make lx-dmesg faster because
> of fewer roundtrips to gdbserver and jtag (or whatever backend you're
> using).
I think this is already covered. utils.read_memoryview uses
inferior.read_memory and I think that reads the entire log buffer at
once (at most 2 reads, one for each half).
next prev parent reply other threads:[~2019-10-11 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 15:03 [PATCH] scripts/gdb: fix lx-dmesg when CONFIG_PRINTK_CALLER is set Joel Colledge
2019-10-10 14:51 ` Joel Colledge
2019-10-10 15:13 ` Jan Kiszka
2019-10-10 19:36 ` Leonard Crestez
2019-10-11 12:24 ` [PATCH v2] " Joel Colledge
2019-10-11 12:38 ` Jan Kiszka
2019-10-11 12:56 ` Joel Colledge
2019-10-11 14:25 ` [PATCH v3] " Joel Colledge
2019-10-11 15:41 ` Jan Kiszka
2019-10-11 12:47 ` [PATCH v2] " Leonard Crestez
2019-10-11 13:01 ` Joel Colledge [this message]
2019-10-11 14:20 ` Leonard Crestez
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='CAGNP_+Wkya-wn-ckAmCoC0Mda=3cBDi4vYeZj-9SWT0EF8ja4w@mail.gmail.com' \
--to=joel.colledge@linbit.com \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=leonard.crestez@nxp.com \
--cc=linux-kernel@vger.kernel.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).