linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: "Christian König" <christian.koenig@amd.com>,
	"Eli Cohen" <elic@nvidia.com>
Cc: daniel.vetter@ffwll.ch, sam@ravnborg.org,
	linux-kernel@vger.kernel.org,
	dri-devel <dri-devel@lists.freedesktop.org>,
	virtualization@lists.linux-foundation.org
Subject: Re: Change eats memory on my server
Date: Mon, 18 Jan 2021 15:48:01 +0100	[thread overview]
Message-ID: <38ddb62c-0b4c-dcc3-e6c2-e025b38d8acd@suse.de> (raw)
In-Reply-To: <b36485a3-2fc6-bf3f-fea2-6a7d040f4df1@amd.com>


[-- Attachment #1.1: Type: text/plain, Size: 1640 bytes --]

Hi

Am 18.01.21 um 14:23 schrieb Christian König:
> Am 18.01.21 um 14:22 schrieb Eli Cohen:
>> On Mon, Jan 18, 2021 at 02:20:49PM +0100, Thomas Zimmermann wrote:
>>> Hi
>>>
>>> Am 18.01.21 um 14:16 schrieb Eli Cohen:
>>>> On Mon, Jan 18, 2021 at 10:30:56AM +0100, Thomas Zimmermann wrote:
>>>>> Here's the patch against the latest DRM tree. v5.11-rc3 should work 
>>>>> as well.
>>>>>
>>>>> I was able to reproduce the memory leak locally and found that the 
>>>>> patch
>>>>> fixes it. Please give it a try.
>>>>>
>>>> As far as I am concerned, this issue is fixed by the patch you sent.
>>>>
>>>> Thanks for looking into it.
>>> OK, great. I'll prepare the real patch soon. Can I add your 
>>> Reported-by and
>>> Tested-by tags?
>> Yes, sure.
> 
> Feel free to add an Acked-by from my side as well.

Done, thanks. I sent out the patch. If no one complains, I'll merge it 
on Wednesday or so.

Best regards
Thomas

> 
> Christian.
> 
>>
>>> Best regards
>>> Thomas
>>>
>>>> Eli
>>>>
>>> -- 
>>> Thomas Zimmermann
>>> Graphics Driver Developer
>>> SUSE Software Solutions Germany GmbH
>>> Maxfeldstr. 5, 90409 Nürnberg, Germany
>>> (HRB 36809, AG Nürnberg)
>>> Geschäftsführer: Felix Imendörffer
>>>
>>
>>
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

      reply	other threads:[~2021-01-18 14:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 15:15 Change eats memory on my server Eli Cohen
2021-01-15  9:03 ` Thomas Zimmermann
2021-01-17  5:08   ` Eli Cohen
2021-01-18  7:43     ` Christian König
2021-01-18  7:49       ` Eli Cohen
2021-01-18  7:57         ` Christian König
2021-01-18  9:12           ` Eli Cohen
2021-01-18  7:54       ` Thomas Zimmermann
2021-01-18  9:13         ` Eli Cohen
2021-01-18  9:30           ` Thomas Zimmermann
2021-01-18 10:39             ` Eli Cohen
2021-01-18 13:16             ` Eli Cohen
2021-01-18 13:20               ` Thomas Zimmermann
2021-01-18 13:22                 ` Eli Cohen
2021-01-18 13:23                   ` Christian König
2021-01-18 14:48                     ` Thomas Zimmermann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38ddb62c-0b4c-dcc3-e6c2-e025b38d8acd@suse.de \
    --to=tzimmermann@suse.de \
    --cc=christian.koenig@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=elic@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).