Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yadav, Sanjay Kumar" <sanjay.kumar.yadav@intel.com>
To: Matthew Auld <matthew.auld@intel.com>, <dri-devel@lists.freedesktop.org>
Cc: intel-xe@lists.freedesktop.org,
	"Christian König" <christian.koenig@amd.com>,
	"Arunpravin Paneer Selvam" <Arunpravin.PaneerSelvam@amd.com>
Subject: Re: [PATCH] gpu/tests/gpu_buddy: Add gpu_test_buddy_alloc_range for exact-range allocation
Date: Mon, 9 Mar 2026 09:33:11 +0530	[thread overview]
Message-ID: <af7c8131-ca80-45c6-8690-1fca823c6059@intel.com> (raw)
In-Reply-To: <9f13e0d0-4a4f-43ac-a2f2-72806b91c92a@intel.com>


On 03-03-2026 16:22, Matthew Auld wrote:
> On 02/03/2026 15:09, Sanjay Yadav wrote:
>> Add a new kunit test gpu_test_buddy_alloc_range() that exercises the
>> __gpu_buddy_alloc_range() exact-range allocation path, triggered when
>> start + size == end with flags=0.
>>
>> The test covers:
>> - Basic exact-range allocation of the full mm
>> - Exact-range allocation of equal sub-ranges (quarters)
>> - Minimum chunk-size exact ranges at start, middle, and end offsets
>> - Non power-of-two mm size with multiple roots, including cross-root
>>    exact-range allocation
>> - Randomized exact-range allocations of N contiguous page-aligned
>>    slices in random order
>> - Negative: partially allocated range must reject overlapping exact
>>    alloc
>> - Negative: checkerboard allocation pattern rejects exact range over
>>    partially occupied pairs
>> - Negative: misaligned start, unaligned size, and out-of-bounds end
>> - Free and re-allocate the same exact range across multiple iterations
>> - Various power-of-two exact ranges at natural alignment
>>
>> Cc: Christian König <christian.koenig@amd.com>
>> Cc: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
>> Suggested-by: Matthew Auld <matthew.auld@intel.com>
>> Signed-off-by: Sanjay Yadav <sanjay.kumar.yadav@intel.com>
>
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Thank you, Matt A., for your prompt review.
Hi Arun,
Kindly request you to review the change, and merge it if everything 
looks good?

      reply	other threads:[~2026-03-09  4:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 15:09 [PATCH] gpu/tests/gpu_buddy: Add gpu_test_buddy_alloc_range for exact-range allocation Sanjay Yadav
2026-03-02 20:59 ` ✓ CI.KUnit: success for " Patchwork
2026-03-02 21:59 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-03  3:41 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-03 10:52 ` [PATCH] " Matthew Auld
2026-03-09  4:03   ` Yadav, Sanjay Kumar [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=af7c8131-ca80-45c6-8690-1fca823c6059@intel.com \
    --to=sanjay.kumar.yadav@intel.com \
    --cc=Arunpravin.PaneerSelvam@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@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