From: Dave Airlie <airlied@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: christian.koenig@amd.com
Subject: [RFC HACKY] ttm don't allow multihop moves
Date: Tue, 20 Oct 2020 14:16:05 +1000 [thread overview]
Message-ID: <20201020041606.1701145-1-airlied@gmail.com> (raw)
This is an RFC for a hacky idea I had to at least move the converation forward.
The branch with this in it is:
https://github.com/airlied/linux/tree/ttm-bounce
it won't apply to any other tree as it's based on all those patches I posted and some other refactorings.
The basic idea is if the driver gets a move request from the TTM core that requires it to bounce the buffer
through another domain, it returns -EMULTIHOP and puts the domain details into the mem_type, the core
code then just does the mem space for the new temp placment, and retries the final placement again.
I've tested on nouveau that the code gets executed (a printk prints at least), and it all doesn't burn
down, but it's very lightly tested.
It does allow getting rid of a lot of driver code to handle bouncing moves.
I'm sure this could be prettier or done in a very different way more effectively, but hey this was
my chance to misuse an errno value.
Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-10-20 4:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 4:16 Dave Airlie [this message]
2020-10-20 4:16 ` [PATCH] [RFC/HACK] drm/ttm: avoid multihop moves in drivers Dave Airlie
2020-10-20 8:30 ` Christian König
2020-10-21 4:42 ` Dave Airlie
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=20201020041606.1701145-1-airlied@gmail.com \
--to=airlied@gmail.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.