[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1b153270-c73f-ea6f-6573-b742b81d6c42@amd.com>
Date: Thu, 25 Oct 2018 07:57:07 +0000
From: "Koenig, Christian" <Christian.Koenig@....com>
To: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
"Zhou, David(ChunMing)" <David1.Zhou@....com>,
Julia Lawall <julia.lawall@...6.fr>
CC: "kbuild-all@...org" <kbuild-all@...org>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
Gustavo Padovan <gustavo@...ovan.org>,
Sean Paul <sean@...rly.run>, David Airlie <airlied@...ux.ie>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drm: fix call_kern.cocci warnings (fwd)
Am 25.10.18 um 09:51 schrieb Maarten Lankhorst:
> Op 25-10-18 om 08:53 schreef Christian König:
>> Am 25.10.18 um 03:28 schrieb Zhou, David(ChunMing):
>>> Reviewed-by: Chunming Zhou <david1.zhou@....com>
>> NAK, GFP_ATOMIC should be avoided.
>>
>> The correct solution is to move the allocation out of the spinlock or drop the lock and reacquire.
> Yeah +1. Especially in a case like this where it's obvious to prevent. :)
Another possibility would to not allocate the dummy fence at all.
E.g. we just need a global instance of that which is always signaled and
has a reference count of +1.
Christian.
Powered by blists - more mailing lists