Messages in this thread | | | From | Leonard Crestez <> | Subject | Re: [PATCH v2] scripts/gdb: fix lx-dmesg when CONFIG_PRINTK_CALLER is set | Date | Fri, 11 Oct 2019 14:20:44 +0000 |
| |
On 11.10.2019 16:02, Joel Colledge wrote: > 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).
You're right, sorry
| |