From: "Paneer Selvam, Arunpravin" <arunpravin.paneerselvam@amd.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
matthew.auld@intel.com, christian.koenig@amd.com,
alexander.deucher@amd.com
Subject: Re: [PATCH] drm/buddy: Fix the range bias clear memory allocation issue
Date: Sun, 12 May 2024 13:33:48 +0530 [thread overview]
Message-ID: <127e58ba-cd09-4fb7-ad9c-7f4b9efdb80b@amd.com> (raw)
In-Reply-To: <Zjs6wVITtRuXoRDz@phenom.ffwll.local>
Hi Daniel,
On 5/8/2024 2:11 PM, Daniel Vetter wrote:
> On Wed, May 08, 2024 at 12:27:20PM +0530, Arunpravin Paneer Selvam wrote:
>> Problem statement: During the system boot time, an application request
>> for the bulk volume of cleared range bias memory when the clear_avail
>> is zero, we dont fallback into normal allocation method as we had an
>> unnecessary clear_avail check which prevents the fallback method leads
>> to fb allocation failure following system goes into unresponsive state.
>>
>> Solution: Remove the unnecessary clear_avail check in the range bias
>> allocation function.
>>
>> Signed-off-by: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
>> Fixes: 96950929eb23 ("drm/buddy: Implement tracking clear page feature")
>> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>> ---
>> drivers/gpu/drm/drm_buddy.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
> Can you please also add a kunit test case to exercise this corner case and
> make sure it stays fixed?
I have sent the v2 along with a kunit test case for this corner case.
Thanks,
Arun.
>
> Thanks, Sima
>> diff --git a/drivers/gpu/drm/drm_buddy.c b/drivers/gpu/drm/drm_buddy.c
>> index 284ebae71cc4..831929ac95eb 100644
>> --- a/drivers/gpu/drm/drm_buddy.c
>> +++ b/drivers/gpu/drm/drm_buddy.c
>> @@ -574,7 +574,7 @@ __drm_buddy_alloc_range_bias(struct drm_buddy *mm,
>>
>> block = __alloc_range_bias(mm, start, end, order,
>> flags, fallback);
>> - if (IS_ERR(block) && mm->clear_avail)
>> + if (IS_ERR(block))
>> return __alloc_range_bias(mm, start, end, order,
>> flags, !fallback);
>>
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2024-05-12 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 6:57 [PATCH] drm/buddy: Fix the range bias clear memory allocation issue Arunpravin Paneer Selvam
2024-05-08 8:41 ` Daniel Vetter
2024-05-12 8:03 ` Paneer Selvam, Arunpravin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-06 13:38 Arunpravin Paneer Selvam
2024-05-07 8:35 ` Matthew Auld
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=127e58ba-cd09-4fb7-ad9c-7f4b9efdb80b@amd.com \
--to=arunpravin.paneerselvam@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).