From: "Koenig, Christian" <Christian.Koenig@amd.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [bug report] drm/ttm: add transparent huge page support for DMA allocations v2
Date: Thu, 27 Jun 2019 17:12:47 +0000 [thread overview]
Message-ID: <278388a6-bd2d-2891-19be-97e33bc470a5@amd.com> (raw)
In-Reply-To: <20190627165532.GD10652@lst.de>
Am 27.06.19 um 18:55 schrieb Christoph Hellwig:
> On Thu, Jun 27, 2019 at 04:19:14PM +0000, Koenig, Christian wrote:
>> If not then the real question is how to correctly get the backing page
>> from dma_alloc_attrs().
> The answer to that is that you can't. dma_alloc_* is an opaque
> allocator that only gives you a kernel virtual address and a dma_addr_t,
> and you can't poke into the internals, as there are a variety of
> different implementations.
Thought that you would say that. It basically confirms my suspicion that
the whole TTM page allocation code is not really working that well.
How do we then do things like mapping that memory to userspace?
And how to we control caching, write combine/back of that memory?
Christian.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-06-27 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 14:06 [bug report] drm/ttm: add transparent huge page support for DMA allocations v2 Dan Carpenter
2019-06-27 16:19 ` Koenig, Christian
[not found] ` <20190627165532.GD10652@lst.de>
2019-06-27 17:12 ` Koenig, Christian [this message]
[not found] ` <20190627171536.GA11117@lst.de>
2019-06-27 17:30 ` Koenig, Christian
[not found] ` <20190628073935.GA29114@lst.de>
2019-06-28 8:05 ` Koenig, Christian
[not found] ` <20190701083117.GA22587@lst.de>
2019-07-15 10:41 ` Koenig, Christian
[not found] ` <20190715125058.GA4384@lst.de>
2019-07-15 13:38 ` Koenig, Christian
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=278388a6-bd2d-2891-19be-97e33bc470a5@amd.com \
--to=christian.koenig@amd.com \
--cc=dan.carpenter@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
/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