From: Matthew Auld <matthew.auld@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org,
Stuart Summers <stuart.summers@intel.com>
Subject: Re: [PATCH] drm/xe: fixup xe_alloc_pf_queue
Date: Thu, 22 Aug 2024 09:54:50 +0100 [thread overview]
Message-ID: <26226783-e6ff-4f68-8b00-ceaadeef9247@intel.com> (raw)
In-Reply-To: <ZsanSW3JhOEmRNfy@DUT025-TGLU.fm.intel.com>
On 22/08/2024 03:49, Matthew Brost wrote:
> On Wed, Aug 21, 2024 at 06:19:18PM +0100, Matthew Auld wrote:
>> kzalloc expects number of bytes, therefore we should convert the number
>> of dw into bytes, otherwise we are likely just accessing beyond the
>> array causing all kinds of carnage. Also fixup the error handling while
>> we are here.
>>
>> Fixes: 3338e4f90c14 ("drm/xe: Use topology to determine page fault queue size")
>> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
>> Cc: Stuart Summers <stuart.summers@intel.com>
>> Cc: Matthew Brost <matthew.brost@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_gt_pagefault.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_gt_pagefault.c b/drivers/gpu/drm/xe/xe_gt_pagefault.c
>> index 401c0527d914..e4510e56e4a2 100644
>> --- a/drivers/gpu/drm/xe/xe_gt_pagefault.c
>> +++ b/drivers/gpu/drm/xe/xe_gt_pagefault.c
>> @@ -417,7 +417,10 @@ static int xe_alloc_pf_queue(struct xe_gt *gt, struct pf_queue *pf_queue)
>> (num_eus + XE_NUM_HW_ENGINES) * PF_MSG_LEN_DW;
>>
>> pf_queue->gt = gt;
>> - pf_queue->data = kzalloc(pf_queue->num_dw, GFP_KERNEL);
>> + pf_queue->data = kzalloc(pf_queue->num_dw * sizeof(u32), GFP_KERNEL);
>
> I merged this s/kzalloc/kcalloc based on feedback from dim.
Thanks.
>
> Matt
>
>> + if (!pf_queue->data)
>> + return -ENOMEM;
>> +
>> spin_lock_init(&pf_queue->lock);
>> INIT_WORK(&pf_queue->worker, pf_queue_work_func);
>>
>> --
>> 2.46.0
>>
prev parent reply other threads:[~2024-08-22 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 17:19 [PATCH] drm/xe: fixup xe_alloc_pf_queue Matthew Auld
2024-08-21 17:46 ` ✓ CI.Patch_applied: success for " Patchwork
2024-08-21 17:47 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-21 17:48 ` ✓ CI.KUnit: success " Patchwork
2024-08-21 17:59 ` ✓ CI.Build: " Patchwork
2024-08-21 18:02 ` ✓ CI.Hooks: " Patchwork
2024-08-21 18:03 ` ✓ CI.checksparse: " Patchwork
2024-08-21 18:15 ` [PATCH] " Nirmoy Das
2024-08-21 18:23 ` ✓ CI.BAT: success for " Patchwork
2024-08-21 23:54 ` ✗ CI.FULL: failure " Patchwork
2024-08-22 2:49 ` [PATCH] " Matthew Brost
2024-08-22 8:54 ` Matthew Auld [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=26226783-e6ff-4f68-8b00-ceaadeef9247@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=stuart.summers@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