From: Matthew Auld <matthew.auld@intel.com>
To: Matthew Brost <matthew.brost@intel.com>,
Tejas Upadhyay <tejas.upadhyay@intel.com>
Cc: intel-xe@lists.freedesktop.org, thomas.hellstrom@linux.intel.com,
himal.prasad.ghimiray@intel.com
Subject: Re: [RFC PATCH V6 2/7] drm/gpu: Add gpu_buddy_addr_to_block helper
Date: Thu, 2 Apr 2026 11:16:10 +0100 [thread overview]
Message-ID: <3297278d-9f36-484c-b4de-8a22545f0b5f@intel.com> (raw)
In-Reply-To: <ac2zqvxb0/hxGPgm@gsse-cloud1.jf.intel.com>
On 02/04/2026 01:09, Matthew Brost wrote:
> On Fri, Mar 27, 2026 at 05:18:15PM +0530, Tejas Upadhyay wrote:
>> Add helper with primary purpose is to efficiently trace a specific
>> physical memory address back to its corresponding TTM buffer object.
>>
>> Signed-off-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
>> ---
>> drivers/gpu/buddy.c | 56 +++++++++++++++++++++++++++++++++++++++
>> include/linux/gpu_buddy.h | 2 ++
>> 2 files changed, 58 insertions(+)
>>
>> diff --git a/drivers/gpu/buddy.c b/drivers/gpu/buddy.c
>> index 52686672e99f..2d26c2a0f971 100644
>> --- a/drivers/gpu/buddy.c
>> +++ b/drivers/gpu/buddy.c
>> @@ -589,6 +589,62 @@ void gpu_buddy_free_block(struct gpu_buddy *mm,
>> }
>> EXPORT_SYMBOL(gpu_buddy_free_block);
>>
>> +/**
>> + * gpu_buddy_addr_to_block - given physical address find a block
>> + *
>> + * @mm: GPU buddy manager
>> + * @addr: Physical address
>> + *
>> + * Returns:
>> + * gpu_buddy_block on success, NULL or error code on failure
>> + */
>> +struct gpu_buddy_block *gpu_buddy_addr_to_block(struct gpu_buddy *mm, u64 addr)
>> +{
>> + struct gpu_buddy_block *block;
>> + LIST_HEAD(dfs);
>> + u64 end;
>> + int i;
>> +
>
> This is somewhat of an orthogonal issue, but we really should update
> gpu_buddy so drivers can register a lock that we can assert is held in
> functions where gpu_buddy manipulates blocks.
>
> Something like this [1].
I think would be a good addition also.
>
> I’ll defer to the gpu_buddy maintainers on whether this code is correct.
>
> Matt
>
> [1] https://elixir.bootlin.com/linux/v6.19.10/source/include/drm/drm_gpusvm.h#L341
>
>> + end = addr + SZ_4K - 1;
>> + for (i = 0; i < mm->n_roots; ++i)
>> + list_add_tail(&mm->roots[i]->tmp_link, &dfs);
>> +
>> + do {
>> + u64 block_start;
>> + u64 block_end;
>> +
>> + block = list_first_entry_or_null(&dfs,
>> + struct gpu_buddy_block,
>> + tmp_link);
>> + if (!block)
>> + break;
>> +
>> + list_del(&block->tmp_link);
>> +
>> + block_start = gpu_buddy_block_offset(block);
>> + block_end = block_start + gpu_buddy_block_size(mm, block) - 1;
>> +
>> + if (!overlaps(addr, end, block_start, block_end))
>> + continue;
>> +
>> + if (contains(addr, end, block_start, block_end) &&
>> + !gpu_buddy_block_is_split(block)) {
>> + if (gpu_buddy_block_is_free(block))
>> + return NULL;
>> + else if (gpu_buddy_block_is_allocated(block) && !mm->clear_avail)
>> + return block;
>> + }
>> +
>> + if (gpu_buddy_block_is_split(block)) {
>> + list_add(&block->right->tmp_link, &dfs);
>> + list_add(&block->left->tmp_link, &dfs);
>> + }
>> + } while (1);
>> +
>> + return ERR_PTR(-ENXIO);
>> +}
>> +EXPORT_SYMBOL(gpu_buddy_addr_to_block);
>> +
>> static void __gpu_buddy_free_list(struct gpu_buddy *mm,
>> struct list_head *objects,
>> bool mark_clear,
>> diff --git a/include/linux/gpu_buddy.h b/include/linux/gpu_buddy.h
>> index 5fa917ba5450..957c69c560bc 100644
>> --- a/include/linux/gpu_buddy.h
>> +++ b/include/linux/gpu_buddy.h
>> @@ -231,6 +231,8 @@ void gpu_buddy_reset_clear(struct gpu_buddy *mm, bool is_clear);
>>
>> void gpu_buddy_free_block(struct gpu_buddy *mm, struct gpu_buddy_block *block);
>>
>> +struct gpu_buddy_block *gpu_buddy_addr_to_block(struct gpu_buddy *mm, u64 addr);
>> +
>> void gpu_buddy_free_list(struct gpu_buddy *mm,
>> struct list_head *objects,
>> unsigned int flags);
>> --
>> 2.52.0
>>
next prev parent reply other threads:[~2026-04-02 10:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 11:48 [RFC PATCH V6 0/7] Add memory page offlining support Tejas Upadhyay
2026-03-27 11:48 ` [RFC PATCH V6 1/7] drm/xe: Link VRAM object with gpu buddy Tejas Upadhyay
2026-04-01 23:56 ` Matthew Brost
2026-04-02 9:10 ` Upadhyay, Tejas
2026-04-02 20:50 ` Matthew Brost
2026-04-06 11:04 ` Upadhyay, Tejas
2026-03-27 11:48 ` [RFC PATCH V6 2/7] drm/gpu: Add gpu_buddy_addr_to_block helper Tejas Upadhyay
2026-04-02 0:09 ` Matthew Brost
2026-04-02 10:16 ` Matthew Auld [this message]
2026-04-02 9:12 ` Matthew Auld
2026-03-27 11:48 ` [RFC PATCH V6 3/7] drm/xe: Handle physical memory address error Tejas Upadhyay
2026-04-01 23:53 ` Matthew Brost
2026-04-02 1:03 ` Matthew Brost
2026-04-02 10:30 ` Upadhyay, Tejas
2026-04-02 20:20 ` Matthew Brost
2026-04-07 12:03 ` Upadhyay, Tejas
2026-03-27 11:48 ` [RFC PATCH V6 4/7] drm/xe/cri: Add debugfs to inject faulty vram address Tejas Upadhyay
2026-03-27 11:48 ` [RFC PATCH V6 5/7] gpu/buddy: Add routine to dump allocated buddy blocks Tejas Upadhyay
2026-03-27 11:48 ` [RFC PATCH V6 6/7] drm/xe/configfs: Add vram bad page reservation policy Tejas Upadhyay
2026-03-27 11:48 ` [RFC PATCH V6 7/7] drm/xe/cri: Add sysfs interface for bad gpu vram pages Tejas Upadhyay
2026-03-27 12:24 ` ✗ CI.checkpatch: warning for Add memory page offlining support (rev6) Patchwork
2026-03-27 12:26 ` ✓ CI.KUnit: success " Patchwork
2026-03-27 13:16 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-28 4:49 ` ✓ Xe.CI.FULL: " 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=3297278d-9f36-484c-b4de-8a22545f0b5f@intel.com \
--to=matthew.auld@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=tejas.upadhyay@intel.com \
--cc=thomas.hellstrom@linux.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