From: Alvin Sun <alvin.sun@linux.dev>
To: Deborah Brouwer <deborah.brouwer@collabora.com>,
Daniel Almeida <daniel.almeida@collabora.com>
Cc: rust-for-linux@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 04/11] drm/tyr: add per-file VM pool
Date: Tue, 20 Oct 2026 22:55:08 +0800 [thread overview]
Message-ID: <5c0856e1dd1ecb48.1792508174@smtp.migadu.com> (raw)
In-Reply-To: <as7IqjINtIURG4yi@um790>
Hi Deborah, Daniel,
On Tue, Oct 13, 2026 at 05:11:22PM -0700, Deborah Brouwer wrote:
> Interesting, I see what you mean because it would give the caller control
> over the vm and managing its tear down. And it would be nice to separate
> the creation of the vm from inserting it into the pool. I implemented this
> myself and that's fine if you want to go with adding a custom VmAddError
> or something like that.
The v4 series is out with the pool reworked using Daniel's AddError
approach, and the rest of your comments addressed.
v4 series: https://lore.kernel.org/r/20261020-tyr-ioctls-v4-0-704de77da223@kylinos.cn
Best regards,
Alvin
next prev parent reply other threads:[~2026-10-20 14:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 2:15 [PATCH v3 00/11] drm/tyr: add VM and BO ioctl support Ke Sun via B4 Relay
2026-09-29 2:15 ` [PATCH v3 01/11] rust: sizes: add SZ_4G constant Ke Sun via B4 Relay
2026-09-29 2:15 ` [PATCH v3 02/11] rust: mm: add `task_size` helper Ke Sun via B4 Relay
2026-09-29 2:15 ` [PATCH v3 03/11] rust: sync: arc: relax `ForeignOwnable` for `Arc<T>` Ke Sun via B4 Relay
2026-09-29 2:15 ` [PATCH v3 04/11] drm/tyr: add per-file VM pool Ke Sun via B4 Relay
2026-10-09 14:22 ` Daniel Almeida
2026-10-10 17:15 ` Deborah Brouwer
2026-10-10 19:33 ` Daniel Almeida
2026-10-14 0:11 ` Deborah Brouwer
2026-10-20 14:55 ` Alvin Sun [this message]
2026-09-29 2:15 ` [PATCH v3 05/11] drm/tyr: add user and MCU VM specifications Ke Sun via B4 Relay
2026-10-09 14:26 ` Daniel Almeida
2026-10-09 14:27 ` Daniel Almeida
2026-09-29 2:15 ` [PATCH v3 06/11] drm/tyr: add BO creation and lookup helpers Ke Sun via B4 Relay
2026-10-09 14:28 ` Daniel Almeida
2026-09-29 2:15 ` [PATCH v3 07/11] drm/tyr: add VM-related ioctls Ke Sun via B4 Relay
2026-10-09 14:36 ` Daniel Almeida
2026-09-29 2:15 ` [PATCH v3 08/11] drm/tyr: add BO-related ioctls Ke Sun via B4 Relay
2026-10-09 14:52 ` Daniel Almeida
2026-09-29 2:15 ` [PATCH v3 09/11] rust: device: expose dma_coherent() Ke Sun via B4 Relay
2026-09-29 18:40 ` Danilo Krummrich
2026-10-20 14:55 ` Alvin Sun
2026-09-29 2:16 ` [PATCH v3 10/11] drm/tyr: gem: flush write-combine BOs from probe-time coherence Ke Sun via B4 Relay
2026-09-29 2:16 ` [PATCH v3 11/11] drm/tyr: gem: map cached BOs for DRM_PANTHOR_BO_WB_MMAP Ke Sun via B4 Relay
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=5c0856e1dd1ecb48.1792508174@smtp.migadu.com \
--to=alvin.sun@linux.dev \
--cc=daniel.almeida@collabora.com \
--cc=deborah.brouwer@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=rust-for-linux@vger.kernel.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