Displaying 7 results from an estimated 7 matches for "debugobj".
2015 Sep 17
7
[PATCH 0/2] Fix memory leaks in virtio & remoteproc cores
Hi,
The following patches fix couple of memory leaks in the virtio and
remoteproc cores when using these as modules, and going through a
cycle of insmod and rmmod with at least a device registered with
the corresponding cores in between. I ran into this on our downstream
product kernels on both 3.14 and 4.1 based kernels, and should apply
to the latest kernel as well.
Patches can be picked up
2015 Sep 17
7
[PATCH 0/2] Fix memory leaks in virtio & remoteproc cores
Hi,
The following patches fix couple of memory leaks in the virtio and
remoteproc cores when using these as modules, and going through a
cycle of insmod and rmmod with at least a device registered with
the corresponding cores in between. I ran into this on our downstream
product kernels on both 3.14 and 4.1 based kernels, and should apply
to the latest kernel as well.
Patches can be picked up
2015 Sep 17
0
DEFINE_IDA causing memory leaks? (was Re: [PATCH 1/2] virtio: fix memory leak of virtio ida cache layers)
...of ida_destroy() tho. I suppose we can rename it to
idr_remove_all() and then do the same to idr. I'm not particularly
objecting to all that but what's wrong with just calling idr_destroy()
on exit paths? If missing the call in modules is an issue, maybe we
can just annotate idr/ida with debugobj?
Thanks.
--
tejun
2015 Sep 17
0
DEFINE_IDA causing memory leaks? (was Re: [PATCH 1/2] virtio: fix memory leak of virtio ida cache layers)
...d be
>
> struct ida someida:
>
> ida_init(&someida);
>
> ...
>
> ida_destroy(&someida);
>
> so the object explicitly has a constructor matched to a destructor.
Yeah, I get that. I'm just not convinced that this matters enough
especially if we can get debugobj/ksan/whatever trip on it.
Thanks.
--
tejun
2018 Mar 26
0
Interest in integrating a linux perf JITEventListener?
...cessfullyInitialized = true;
> +}
> +
> +void PerfJITEventListener::NotifyObjectEmitted(
> + const ObjectFile &Obj,
> + const RuntimeDyld::LoadedObjectInfo &L) {
> +
> + if (!SuccessfullyInitialized)
> + return;
> +
> + OwningBinary<ObjectFile> DebugObjOwner = L.getObjectForDebug(Obj);
> + const ObjectFile &DebugObj = *DebugObjOwner.getBinary();
> +
> + // Get the address of the object image for use as a unique identifier
> + DWARFContextInMemory Context(DebugObj);
> +
> + // Use symbol info to iterate functions in the ob...
2016 Dec 29
1
Interest in integrating a linux perf JITEventListener?
Having something like this available in tree would definitely be
useful. For simplicity, why don't we start with support for the second
style? This is the long term useful one and would be a good starting
point for getting the code in tree. Can you give a pointer to the patch
so that I can assess the rough complexity? If it's simple enough, I'd
be happy to help get it reviewed
2017 Feb 02
0
Interest in integrating a linux perf JITEventListener?
Hi,
On 2016-12-29 13:17:50 -0800, Philip Reames wrote:
> Having something like this available in tree would definitely be
> useful.
Cool.
> For simplicity, why don't we start with support for the second style? This
> is the long term useful one and would be a good starting point for getting
> the code in tree.
Works for me.
> Can you give a pointer to the patch so that