Hi Andrew,
On 23/12/2020 16:34, Andrew Cooper wrote:
Wrappers for xmalloc() and friends, which track allocations tied to a specific
domain.
Check for any leaked memory at domain destruction time.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Roger Pau Monné
CC: Wei Liu
CC: Stefano S
On 14/01/2021 10:14, Jan Beulich wrote:
> On 14.01.2021 00:16, Andrew Cooper wrote:
>> On 05/01/2021 15:56, Jan Beulich wrote:
>>> On 23.12.2020 17:34, Andrew Cooper wrote:
RFC:
* This probably wants to be less fatal in release builds
>>> I'm not even convinced this wants to be a panic()
On 14.01.2021 00:16, Andrew Cooper wrote:
> On 05/01/2021 15:56, Jan Beulich wrote:
>> On 23.12.2020 17:34, Andrew Cooper wrote:
>>> RFC:
>>> * This probably wants to be less fatal in release builds
>> I'm not even convinced this wants to be a panic() in debug builds.
>
> Any memory leak spotted
On 05/01/2021 15:56, Jan Beulich wrote:
> On 23.12.2020 17:34, Andrew Cooper wrote:
>> RFC:
>> * This probably wants to be less fatal in release builds
> I'm not even convinced this wants to be a panic() in debug builds.
Any memory leak spotted by this is an XSA, except in the narrow case of
bein
On 23.12.2020 17:34, Andrew Cooper wrote:
> --- /dev/null
> +++ b/xen/common/dmalloc.c
> @@ -0,0 +1,19 @@
> +#include
> +#include
> +#include
> +
> +void dfree(struct domain *d, void *ptr)
> +{
> +atomic_dec(&d->dalloc_heap);
> +xfree(ptr);
> +}
> +
> +void *_dzalloc(struct domain *d, si
On 23.12.2020 17:34, Andrew Cooper wrote:
> RFC:
> * This probably wants to be less fatal in release builds
I'm not even convinced this wants to be a panic() in debug builds.
> * In an ideal world, we'd also want to count the total number of bytes
>allocated from the xmalloc heap, which wou
Wrappers for xmalloc() and friends, which track allocations tied to a specific
domain.
Check for any leaked memory at domain destruction time.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Roger Pau Monné
CC: Wei Liu
CC: Stefano Stabellini
CC: Julien Grall
CC: Volodymyr Babchuk
CC:
