From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Breton M. Saunders" <brett@mynah-software.com>
Subject: Re: significant ioremap leak in i915?
Date: Sun, 12 Oct 2014 12:07:06 +0100
Message-ID: <543A60DA.1020200@mynah-software.com>
References: <543A49B8.20400@mynah-software.com>
 <CAPM=9tziAwd7pF7YX8ipWRbEJcX+S2AvDp5-gC24_=o+WALMqQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces@lists.freedesktop.org>
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10])
 by gabe.freedesktop.org (Postfix) with ESMTP id 487226E05E
 for <intel-gfx@lists.freedesktop.org>; Sun, 12 Oct 2014 04:07:13 -0700 (PDT)
In-Reply-To: <CAPM=9tziAwd7pF7YX8ipWRbEJcX+S2AvDp5-gC24_=o+WALMqQ@mail.gmail.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Errors-To: intel-gfx-bounces@lists.freedesktop.org
Sender: "Intel-gfx" <intel-gfx-bounces@lists.freedesktop.org>
To: Dave Airlie <airlied@gmail.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
List-Id: intel-gfx@lists.freedesktop.org

On 12/10/14 11:23, Dave Airlie wrote:
> On 12 October 2014 19:28, Breton M. Saunders <brett@mynah-software.com> wrote:
>> Guys,
>>
>>    This might be covered elsewhere, but help me come up to speed:  I am
>> trying to analyze a leak in i915 that occurs on a digital sinage system that
>> I've built.  The system basically is doing a lot of XCompositeRedirectWindow
>> / glXBindTexImageEXT calls to render web views and mplayer output onto
>> opengl textures for subsequent rendering.
>>
>>    In my testing, I observe that an enormous block is being lost in ioremap
>> by looking at /proc/vmallocinfo:
>>
>> <snip>
>> 0xffffc90000200000-0xffffc90010201000 268439552 pci_mmcfg_arch_map+0x33/0x90
>> phys=e0000000 ioremap
>> <snip>
>> 0xffffc90010f80000-0xffffc90020f81000 268439552 i915_driver_load+0x20c/0x6d0
>> [i915] phys=c0000000 ioremap
>> <snip>
>>
>>    So in this example 268 megabytes have been lost.
>
> This isn't RAM, its address space mapping, its not really a leak at all.
It really doesn't matter whether it is ram or mapping; its a resource 
leak that causes the system to OOM and panic.

     -Brett