From: Andrzej Hajda <andrzej.hajda@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: limit lmem allocation size to succeed on SmallBars
Date: Mon, 5 Jun 2023 11:06:51 +0200 [thread overview]
Message-ID: <f308a7e7-011d-bc32-a9c5-877911bd0e30@intel.com> (raw)
In-Reply-To: <ZHmxXYT0ZcRlpJXI@ashyti-mobl2.lan>
On 02.06.2023 11:07, Andi Shyti wrote:
> Hi Andrzej,
>
> On Thu, Jun 01, 2023 at 04:44:50PM +0200, Andrzej Hajda wrote:
>> In case system is short on mappable memory (256MB on SmallBar) allocation
>> of two 1GB buffers will fail.
>>
>> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/8300
>> Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
>> ---
>> drivers/gpu/drm/i915/gt/selftest_tlb.c | 11 +++++++++--
>> 1 file changed, 9 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/selftest_tlb.c b/drivers/gpu/drm/i915/gt/selftest_tlb.c
>> index 4493c8518e91b2..3bd6b540257b46 100644
>> --- a/drivers/gpu/drm/i915/gt/selftest_tlb.c
>> +++ b/drivers/gpu/drm/i915/gt/selftest_tlb.c
>> @@ -190,11 +190,18 @@ pte_tlbinv(struct intel_context *ce,
>>
>> static struct drm_i915_gem_object *create_lmem(struct intel_gt *gt)
>> {
>> + struct intel_memory_region *mr = gt->i915->mm.regions[INTEL_REGION_LMEM_0];
>> + resource_size_t size = SZ_1G;
>> +
>> /*
>> * Allocation of largest possible page size allows to test all types
>> - * of pages.
>> + * of pages. To succeed with both allocations, especially in case of Small
>> + * BAR, try to allocate no more than quarter of mappable memory.
>> */
>> - return i915_gem_object_create_lmem(gt->i915, SZ_1G, I915_BO_ALLOC_CONTIGUOUS);
>> + if (mr && size > mr->io_size / 4)
>> + size = mr->io_size / 4;
>> +
>> + return i915_gem_object_create_lmem(gt->i915, size, I915_BO_ALLOC_CONTIGUOUS);
>
> makes sense to me.
>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Thx, patch merged.
Regards
Andrzej
>
> Thanks,
> Andi
next prev parent reply other threads:[~2023-06-05 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 14:44 [Intel-gfx] [PATCH] drm/i915/gt: limit lmem allocation size to succeed on SmallBars Andrzej Hajda
2023-06-01 21:00 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-06-02 9:07 ` [Intel-gfx] [PATCH] " Andi Shyti
2023-06-05 9:06 ` Andrzej Hajda [this message]
2023-06-03 22:45 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
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=f308a7e7-011d-bc32-a9c5-877911bd0e30@intel.com \
--to=andrzej.hajda@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nirmoy.das@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