Re: [PATCH 1/1] arch/um: fix forward declaration for vmalloc

2024-04-22 Thread Richard Weinberger
- Ursprüngliche Mail - > Von: "Suren Baghdasaryan" >> > It's in mm-unstable under dc26c7e79daf2fc11169b23c150862f0e878ee5a. I >> > think it just didn't reach Linus' tree yet. >> >> Hmm, so we better postpone this path until said commit hits Linus tree, >> or you carry it together with the

Re: [PATCH 1/1] arch/um: fix forward declaration for vmalloc

2024-04-22 Thread Suren Baghdasaryan
On Mon, Apr 22, 2024 at 1:31 PM Richard Weinberger wrote: > > - Ursprüngliche Mail - > > Von: "Suren Baghdasaryan" > >> > Fixes: 576477564ede ("mm: vmalloc: enable memory allocation profiling") > >> > >> This commit id is not in Linus tree. > >> Do I miss something? > > > > It's in mm-uns

Re: [PATCH 1/1] arch/um: fix forward declaration for vmalloc

2024-04-22 Thread Richard Weinberger
- Ursprüngliche Mail - > Von: "Suren Baghdasaryan" >> > Fixes: 576477564ede ("mm: vmalloc: enable memory allocation profiling") >> >> This commit id is not in Linus tree. >> Do I miss something? > > It's in mm-unstable under dc26c7e79daf2fc11169b23c150862f0e878ee5a. I > think it just didn

Re: [PATCH 1/1] arch/um: fix forward declaration for vmalloc

2024-04-22 Thread Suren Baghdasaryan
On Mon, Apr 22, 2024 at 1:11 PM Richard Weinberger wrote: > > - Ursprüngliche Mail - > > Von: "Suren Baghdasaryan" > > Betreff: [PATCH 1/1] arch/um: fix forward declaration for vmalloc > > > Patch [1] replaced vmalloc() function with a new definition

Re: [PATCH 1/1] arch/um: fix forward declaration for vmalloc

2024-04-22 Thread Richard Weinberger
- Ursprüngliche Mail - > Von: "Suren Baghdasaryan" > Betreff: [PATCH 1/1] arch/um: fix forward declaration for vmalloc > Patch [1] replaced vmalloc() function with a new definition but it did > not adjust the forward declaration used in UML architecture. Change

Re: [PATCH 1/1] arch/um: fix forward declaration for vmalloc

2024-03-28 Thread Johannes Berg
On Tue, 2024-03-26 at 00:37 -0700, Suren Baghdasaryan wrote: > > -extern void *vmalloc(unsigned long size); > +extern void *vmalloc_noprof(unsigned long size); > +#define vmalloc(...) vmalloc_noprof(__VA_ARGS__) > I was confused a bit by the define at first, but that's because this is a

Re: [PATCH 1/1] arch/um: fix forward declaration for vmalloc

2024-03-26 Thread SeongJae Park
On Tue, 26 Mar 2024 00:37:50 -0700 Suren Baghdasaryan wrote: > Patch [1] replaced vmalloc() function with a new definition but it did > not adjust the forward declaration used in UML architecture. Change it > to act as before. > Note that this prevents the vmalloc() allocations in __wrap_malloc()

[PATCH 1/1] arch/um: fix forward declaration for vmalloc

2024-03-26 Thread Suren Baghdasaryan
Patch [1] replaced vmalloc() function with a new definition but it did not adjust the forward declaration used in UML architecture. Change it to act as before. Note that this prevents the vmalloc() allocations in __wrap_malloc() from being accounted. If accounting here is critical, we will have to