From: "Christian König via Virtualization" <virtualization@lists.linux-foundation.org>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>,
David Airlie <airlied@linux.ie>, Huang Rui <ray.huang@amd.com>,
Daniel Vetter <daniel@ffwll.ch>,
Trigger Huang <Trigger.Huang@gmail.com>,
Gert Wollny <gert.wollny@collabora.com>,
Antonio Caggiano <antonio.caggiano@collabora.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
Dmitry Osipenko <digetx@gmail.com>,
kernel@collabora.com
Subject: Re: [PATCH v1] drm/ttm: Refcount allocated tail pages
Date: Mon, 15 Aug 2022 13:28:11 +0200 [thread overview]
Message-ID: <8f749cd0-9a04-7c72-6a4f-a42d501e1489@amd.com> (raw)
In-Reply-To: <86a87de8-24a9-3c53-3ac7-612ca97e41df@collabora.com>
Am 15.08.22 um 13:19 schrieb Dmitry Osipenko:
> [SNIP]
>>>> I'll try to dig out the older discussions, thank you for the quick
>>>> reply!
>>> Are you sure it was really discussed in public previously? All I can
>>> find is yours two answers to a similar patches where you're saying that
>>> this it's a wrong solution without in-depth explanation and further
>>> discussions.
>> Yeah, that's my problem as well I can't find that of hand.
>>
>> But yes it certainly was discussed in public.
> If it was only CC'd to dri-devel, then could be that emails didn't pass
> the spam moderation :/
That might be possible.
>>> Maybe it was discussed privately? In this case I will be happy to get
>>> more info from you about the root of the problem so I could start to
>>> look at how to fix it properly. It's not apparent where the problem is
>>> to a TTM newbie like me.
>>>
>> Well this is completely unfixable. See the whole purpose of TTM is to
>> allow tracing where what is mapped of a buffer object.
>>
>> If you circumvent that and increase the page reference yourself than
>> that whole functionality can't work correctly any more.
> Are you suggesting that the problem is that TTM doesn't see the KVM page
> faults/mappings?
Yes, and no. It's one of the issues, but there is more behind that (e.g.
what happens when TTM switches from pages to local memory for backing a BO).
Another question is why is KVM accessing the page structure in the first
place? The VMA is mapped with VM_PFNMAP and VM_IO, KVM should never ever
touch any of those pages.
Regards,
Christian.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-08-15 11:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220815095423.11131-1-dmitry.osipenko@collabora.com>
2022-08-15 10:05 ` [PATCH v1] drm/ttm: Refcount allocated tail pages Christian König via Virtualization
[not found] ` <134bce02-58d6-8553-bb73-42dfda18a595@collabora.com>
2022-08-15 10:11 ` Christian König via Virtualization
2022-08-15 10:14 ` Christian König via Virtualization
[not found] ` <14be3b22-1d60-732b-c695-ddacc6b21055@collabora.com>
2022-08-15 10:42 ` Christian König via Virtualization
[not found] ` <2df57a30-2afb-23dc-c7f5-f61c113dd5b4@collabora.com>
2022-08-15 10:51 ` Christian König via Virtualization
[not found] ` <86a87de8-24a9-3c53-3ac7-612ca97e41df@collabora.com>
2022-08-15 11:28 ` Christian König via Virtualization [this message]
[not found] ` <5340d876-62b8-8a64-aa6d-7736c2c8710f@collabora.com>
2022-08-15 13:06 ` Christian König via Virtualization
[not found] ` <6893d5e9-4b60-0efb-2a87-698b1bcda63e@collabora.com>
2022-08-15 13:53 ` Christian König via Virtualization
[not found] ` <c9d89644-409e-0363-69f0-a3b8f2ef0ae4@collabora.com>
[not found] ` <6effcd33-8cc3-a4e0-3608-b9cef7a76da7@collabora.com>
[not found] ` <ff28e1b4-cda2-14b8-b9bf-10706ae52cac@collabora.com>
[not found] ` <48b5dd12-b0df-3cc6-a72d-f35156679844@collabora.com>
2022-08-18 9:41 ` Christian König via Virtualization
2022-09-06 20:01 ` Daniel Vetter
2022-09-06 20:05 ` Daniel Vetter
2022-09-07 6:48 ` Christian König via Virtualization
2022-09-08 11:04 ` Rob Clark
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=8f749cd0-9a04-7c72-6a4f-a42d501e1489@amd.com \
--to=virtualization@lists.linux-foundation.org \
--cc=Trigger.Huang@gmail.com \
--cc=airlied@linux.ie \
--cc=antonio.caggiano@collabora.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=digetx@gmail.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gert.wollny@collabora.com \
--cc=kernel@collabora.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray.huang@amd.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