On Sat, Jul 13, 2019 at 2:14 AM Joe Perches wrote:
>
> On Fri, 2019-07-12 at 15:36 -0700, David Miller wrote:
> > From: Arnd Bergmann
> > Date: Fri, 12 Jul 2019 11:06:33 +0200
> >
> > > The cudbg_collect_mem_region() and cudbg_read_fw_mem() both use several
> > > hundred kilobytes of kernel stack
On Fri, 2019-07-12 at 15:36 -0700, David Miller wrote:
> From: Arnd Bergmann
> Date: Fri, 12 Jul 2019 11:06:33 +0200
>
> > The cudbg_collect_mem_region() and cudbg_read_fw_mem() both use several
> > hundred kilobytes of kernel stack space.
Several hundred 'kilo' bytes?
I hope not.
From: Arnd Bergmann
Date: Fri, 12 Jul 2019 11:06:33 +0200
> The cudbg_collect_mem_region() and cudbg_read_fw_mem() both use several
> hundred kilobytes of kernel stack space. One gets inlined into the other,
> which causes the stack usage to be combined beyond the warning limit
> when building wi
The cudbg_collect_mem_region() and cudbg_read_fw_mem() both use several
hundred kilobytes of kernel stack space. One gets inlined into the other,
which causes the stack usage to be combined beyond the warning limit
when building with clang:
drivers/net/ethernet/chelsio/cxgb4/cudbg_lib.c:1057:12: e
4 matches
Mail list logo