Messages in this thread | | | From | Joel Colledge <> | Date | Fri, 11 Oct 2019 15:01:55 +0200 | Subject | Re: [PATCH v2] scripts/gdb: fix lx-dmesg when CONFIG_PRINTK_CALLER is set |
| |
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).
| |