From: "Christian König" <christian.koenig@amd.com>
To: "Chauhan, Madhav" <Madhav.Chauhan@amd.com>,
"Patel, Mihir" <Mihir.Patel@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Kamliya, Prakash" <Prakash.Kamliya@amd.com>,
"Surampalli, Kishore" <Kishore.Surampalli@amd.com>
Subject: Re: [PATCH v3] drm/amdgpu: Add debugfs entry for printing VM info
Date: Tue, 13 Oct 2020 19:04:21 +0200 [thread overview]
Message-ID: <8972977b-be77-496f-d801-9c52bbf2e7c6@amd.com> (raw)
In-Reply-To: <BL0PR12MB2433165202ECE6FF54999D809C040@BL0PR12MB2433.namprd12.prod.outlook.com>
[SNIP]
> Thinking a bit more about it, when you also look at
> bo->preferred_domains and compare that with the current domain you can
> also figure out if a BO is swapped out or not.
>
> Christian.
>
> Thanks Christian for quick review/help and details. Summarizing your inputs and some queries:
> 1. Adding BO from all the lists will give the total amount of memory allocated by this PID
Well you need to add the "done" list again, but otherwise that's correct.
> 2. We can also print bo->preferred domain to check what user asked for and where it is currently.
> But we can have a situation where user asked for VRAM but allowed domain added GTT and we eventually
> Allocated BO in GTT.
Yes, that is correct as well.
> So do we update bo->preferred_domain in that scenario??
No, bo->preferred_domains always reflect what userspace asked for.
> 3. What will be the scenario in which we add BO to the Reloacted/Moved/Idle?? How it is different from Evicted??
We differentiate BOs by per VM and normal. Per VM are for example page
tables and BOs which can't be shared between processes. Those you will
find on the relocated/moved/idle list.
"Normal" BOs can be shared between processes and have a separate lock.
Those you will find on the invalidated/done list.
Regards,
Christian.
>
> Regards,
> Madhav
>
>> Christian.
>>
>>> Regards,
>>> Mihir
>>>> Thanks,
>>>> Mihir
>> _______________________________________________
>> amd-gfx mailing list
>> amd-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2020-10-13 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 9:01 [PATCH v3] drm/amdgpu: Add debugfs entry for printing VM info Mihir Patel
2020-10-12 9:10 ` Christian König
2020-10-12 9:37 ` Patel, Mihir
2020-10-12 9:44 ` Christian König
2020-10-12 10:00 ` Patel, Mihir
2020-10-12 10:50 ` Christian König
2020-10-12 10:54 ` Christian König
2020-10-12 11:51 ` Patel, Mihir
2020-10-13 12:19 ` Chauhan, Madhav
2020-10-13 17:04 ` Christian König [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=8972977b-be77-496f-d801-9c52bbf2e7c6@amd.com \
--to=christian.koenig@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Kishore.Surampalli@amd.com \
--cc=Madhav.Chauhan@amd.com \
--cc=Mihir.Patel@amd.com \
--cc=Prakash.Kamliya@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
/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