[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1603020958450.3516@vshiva-Udesk>
Date: Wed, 2 Mar 2016 09:59:47 -0800 (PST)
From: Vikas Shivappa <vikas.shivappa@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>
cc: Vikas Shivappa <vikas.shivappa@...ux.intel.com>,
vikas.shivappa@...el.com, linux-kernel@...r.kernel.org,
x86@...nel.org, hpa@...or.com, mingo@...nel.org,
peterz@...radead.org, ravi.v.shankar@...el.com,
tony.luck@...el.com, fenghua.yu@...el.com, h.peter.anvin@...el.com
Subject: Re: [PATCH 3/6] x86/mbm: Intel Memory B/W Monitoring enumeration
and init
On Wed, 2 Mar 2016, Thomas Gleixner wrote:
> On Tue, 1 Mar 2016, Vikas Shivappa wrote:
>> @@ -1397,8 +1543,11 @@ static int __init intel_cqm_init(void)
>> __perf_cpu_notifier(intel_cqm_cpu_notifier);
>> out:
>> cpu_notifier_register_done();
>> - if (ret)
>> + if (ret) {
>> + mbm_enabled = false;
>> + cqm_enabled = false;
>> kfree(str);
>
>
> Leaks mbm_local and mbm_total ....
Will fix. Thanks for pointing out. I missed the ones which are done at the
next level of calls from the init. Will do a check on all the globals as well.
Vikas
>
>> + }
>>
>> return ret;
>> }
>> --
>> 1.9.1
>>
>>
>
Powered by blists - more mailing lists