On Sat, 22 Jun 2019 at 13:10, Simon Glass wrote:
>
> On Fri, 14 Jun 2019 at 20:51, Heinrich Schuchardt wrote:
> >
> > There is no good reason to limit the trace buffer to 2GiB on a 64bit
> > system. Adjust the types of the relevant parameters.
> >
> > Signed-off-by: Heinrich Schuchardt
> > ---
>
Hi Heinrich,
OK...I can't remember the details but there is a tool that does that. The
format that U-Boot's proftool emits is pretty standard. I recall using it
with a tool the kernel uses to get info like you are looking for.
Regards,
Simon
On Mon, 24 Jun 2019 at 11:30, Heinrich Schuchardt
wr
On 6/24/19 3:56 PM, Simon Glass wrote:
Hi Heinrich,
On Sat, 22 Jun 2019 at 20:37, Heinrich Schuchardt wrote:
On 6/22/19 9:10 PM, Simon Glass wrote:
On Fri, 14 Jun 2019 at 20:51, Heinrich Schuchardt wrote:
There is no good reason to limit the trace buffer to 2GiB on a 64bit
system. Adjust
Hi Heinrich,
On Sat, 22 Jun 2019 at 20:37, Heinrich Schuchardt wrote:
>
> On 6/22/19 9:10 PM, Simon Glass wrote:
> > On Fri, 14 Jun 2019 at 20:51, Heinrich Schuchardt
> > wrote:
> >>
> >> There is no good reason to limit the trace buffer to 2GiB on a 64bit
> >> system. Adjust the types of the r
On 6/22/19 9:10 PM, Simon Glass wrote:
On Fri, 14 Jun 2019 at 20:51, Heinrich Schuchardt wrote:
There is no good reason to limit the trace buffer to 2GiB on a 64bit
system. Adjust the types of the relevant parameters.
Signed-off-by: Heinrich Schuchardt
---
cmd/trace.c | 10 --
On Fri, 14 Jun 2019 at 20:51, Heinrich Schuchardt wrote:
>
> There is no good reason to limit the trace buffer to 2GiB on a 64bit
> system. Adjust the types of the relevant parameters.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> cmd/trace.c | 10 --
> include/trace.h | 6 +++---
There is no good reason to limit the trace buffer to 2GiB on a 64bit
system. Adjust the types of the relevant parameters.
Signed-off-by: Heinrich Schuchardt
---
cmd/trace.c | 10 --
include/trace.h | 6 +++---
lib/trace.c | 14 +++---
tools/proftool.c | 4 ++--
4 fil
7 matches
Mail list logo
