From: Zack Rusin <zackr@vmware.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: "Das, Nirmoy" <Nirmoy.Das@amd.com>,
Linux-graphics-maintainer <Linux-graphics-maintainer@vmware.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [Linux-graphics-maintainer] [PATCH 2/3] drm/ttm: move memory accounting into vmwgfx v3
Date: Mon, 8 Feb 2021 20:40:20 +0000 [thread overview]
Message-ID: <8516A633-8DA6-44D2-A414-59473AB2C3F8@vmware.com> (raw)
In-Reply-To: <8750d410-6212-efe2-af55-4974c6cdf092@amd.com>
> On Feb 8, 2021, at 15:23, Christian König <christian.koenig@amd.com> wrote:
>
> Am 08.02.21 um 21:21 schrieb Zack Rusin:
>>> On Feb 8, 2021, at 08:35, Christian König <christian.koenig@amd.com> wrote:
>>>
>>> Hi Zack,
>>>
>>> ok we figured out how to do this correctly.
>>>
>>> Basically using the pdev->kobj instead of the drm->primary->kdev->kobj pointer worked quite well.
>>>
>>> I've just send the latest patches to the mailing list. If you don't have any objections I will commit that tomorrow with your and Daniels rb.
>> That sounds good. That moves the entries under /sys/devices/pciBUS/ID/memory_accounting , yes?
>
> Yes correct. I really hope nobody relied on the old location or otherwise I need to add some kind of symlink workaround or such.
I’m not aware of anyone depending on that location. I’ll think about it this week and in the worst case I’ll just disable it for the next release until we can spend some time creating an actual structure to our sysfs layout that we can maintain long term but that’s not something you need to worry about. Thank you.
z
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-02-08 20:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 13:16 [PATCH 1/3] drm/ttm: rework ttm_tt page limit v3 Christian König
2021-01-28 13:16 ` [PATCH 2/3] drm/ttm: move memory accounting into vmwgfx v3 Christian König
2021-02-02 13:04 ` Christian König
2021-02-02 15:14 ` Zack Rusin
2021-02-02 15:16 ` Christian König
2021-02-02 17:42 ` Zack Rusin
2021-02-03 2:45 ` [Linux-graphics-maintainer] " Zack Rusin
2021-02-03 8:20 ` Christian König
2021-02-08 13:35 ` Christian König
2021-02-08 13:39 ` Daniel Vetter
2021-02-08 20:21 ` Zack Rusin
2021-02-08 20:23 ` Christian König
2021-02-08 20:40 ` Zack Rusin [this message]
2021-01-28 13:16 ` [PATCH 3/3] drm/ttm: drop sysfs directory Christian König
2021-02-03 11:28 ` Daniel Vetter
2021-02-03 11:26 ` [PATCH 1/3] drm/ttm: rework ttm_tt page limit v3 Daniel Vetter
2021-02-03 12:18 ` Christian König
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=8516A633-8DA6-44D2-A414-59473AB2C3F8@vmware.com \
--to=zackr@vmware.com \
--cc=Linux-graphics-maintainer@vmware.com \
--cc=Nirmoy.Das@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.