Re: [PATCH 11/40] lmb: make LMB memory map persistent and global

2024-08-15 Thread Caleb Connolly
Hi, On 24/07/2024 08:01, Sughosh Ganu wrote: The current LMB API's for allocating and reserving memory use a per-caller based memory view. Memory allocated by a caller can then be overwritten by another caller. Make these allocations and reservations persistent using the alloced list data struct

Re: [PATCH 11/40] lmb: make LMB memory map persistent and global

2024-07-30 Thread Sughosh Ganu
On Wed, 31 Jul 2024 at 01:17, Simon Glass wrote: > > Hi Sughosh, > > On Wed, 24 Jul 2024 at 00:03, Sughosh Ganu wrote: > > > > The current LMB API's for allocating and reserving memory use a > > per-caller based memory view. Memory allocated by a caller can then be > > overwritten by another call

Re: [PATCH 11/40] lmb: make LMB memory map persistent and global

2024-07-30 Thread Simon Glass
Hi Sughosh, On Wed, 24 Jul 2024 at 00:03, Sughosh Ganu wrote: > > The current LMB API's for allocating and reserving memory use a > per-caller based memory view. Memory allocated by a caller can then be > overwritten by another caller. Make these allocations and reservations > persistent using th

Re: [PATCH 11/40] lmb: make LMB memory map persistent and global

2024-07-29 Thread Simon Glass
Hi Sughosh, On Mon, 29 Jul 2024 at 01:50, Sughosh Ganu wrote: > > On Fri, 26 Jul 2024 at 05:02, Simon Glass wrote: > > > > Hi Sughosh, > > > > On Wed, 24 Jul 2024 at 00:03, Sughosh Ganu wrote: > > > > > > The current LMB API's for allocating and reserving memory use a > > > per-caller based mem

Re: [PATCH 11/40] lmb: make LMB memory map persistent and global

2024-07-29 Thread Sughosh Ganu
On Fri, 26 Jul 2024 at 05:02, Simon Glass wrote: > > Hi Sughosh, > > On Wed, 24 Jul 2024 at 00:03, Sughosh Ganu wrote: > > > > The current LMB API's for allocating and reserving memory use a > > per-caller based memory view. Memory allocated by a caller can then be > > overwritten by another call

Re: [PATCH 11/40] lmb: make LMB memory map persistent and global

2024-07-25 Thread Simon Glass
Hi Sughosh, On Wed, 24 Jul 2024 at 00:03, Sughosh Ganu wrote: > > The current LMB API's for allocating and reserving memory use a > per-caller based memory view. Memory allocated by a caller can then be > overwritten by another caller. Make these allocations and reservations > persistent using th

[PATCH 11/40] lmb: make LMB memory map persistent and global

2024-07-23 Thread Sughosh Ganu
The current LMB API's for allocating and reserving memory use a per-caller based memory view. Memory allocated by a caller can then be overwritten by another caller. Make these allocations and reservations persistent using the alloced list data structure. Two alloced lists are declared -- one for