From: hch@infradead.org (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: noveau vs arm dma ops
Date: Wed, 25 Apr 2018 01:54:39 -0700 [thread overview]
Message-ID: <20180425085439.GA29996@infradead.org> (raw)
In-Reply-To: <20180425074151.GA2271@ulmo>
[discussion about this patch, which should have been cced to the iommu
and linux-arm-kernel lists, but wasn't:
https://www.spinics.net/lists/dri-devel/msg173630.html]
On Wed, Apr 25, 2018 at 09:41:51AM +0200, Thierry Reding wrote:
> > API from the iommu/dma-mapping code. Drivers have no business poking
> > into these details.
>
> The interfaces that the above patch uses are all EXPORT_SYMBOL_GPL,
> which is rather misleading if they are not meant to be used by drivers
> directly.
The only reason the DMA ops are exported is because get_arch_dma_ops
references (or in case of the coherent ones used to reference). We
don't let drivers assign random dma ops.
>
> > Thierry, please resend this with at least the iommu list and
> > linux-arm-kernel in Cc to have a proper discussion on the right API.
>
> I'm certainly open to help with finding a correct solution, but the
> patch above was purposefully terse because this is something that I
> hope we can get backported to v4.16 to unbreak Nouveau. Coordinating
> such a backport between ARM and DRM trees does not sound like something
> that would help getting this fixed in v4.16.
Coordinating the backport of a trivial helper in the arm tree is not
the end of the world. Really, this cowboy attitude is a good reason
why graphics folks have such a bad rep. You keep poking into random
kernel internals, don't talk to anoyone and then complain if people
are upset. This shouldn't be surprising.
> Granted, this issue could've been caught with a little more testing, but
> in retrospect I think it would've been a lot better if ARM_DMA_USE_IOMMU
> was just enabled unconditionally if it has side-effects that platforms
> don't opt in to but have to explicitly opt out of.
Agreed on that count. Please send a patch.
next parent reply other threads:[~2018-04-25 8:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f1100bd6-dd98-55a9-a92f-1cad919f235f@amd.com>
[not found] ` <20180420124625.GA31078@infradead.org>
[not found] ` <20180420152111.GR31310@phenom.ffwll.local>
[not found] ` <20180424184847.GA3247@infradead.org>
[not found] ` <CAKMK7uFL68pu+-9LODTgz+GQYvxpnXOGhxfz9zorJ_JKsPVw2g@mail.gmail.com>
[not found] ` <20180425054855.GA17038@infradead.org>
[not found] ` <CAKMK7uEFitkNQrD6cLX5Txe11XhVO=LC4YKJXH=VNdq+CY=DjQ@mail.gmail.com>
[not found] ` <CAKMK7uFx=KB1vup=WhPCyfUFairKQcRR4BEd7aXaX1Pj-vj3Cw@mail.gmail.com>
[not found] ` <20180425064335.GB28100@infradead.org>
[not found] ` <20180425074151.GA2271@ulmo>
2018-04-25 8:54 ` Christoph Hellwig [this message]
2018-04-25 9:25 ` noveau vs arm dma ops Russell King - ARM Linux
2018-04-25 10:04 ` Daniel Vetter
2018-04-25 15:33 ` Christoph Hellwig
2018-04-25 21:35 ` Daniel Vetter
2018-04-25 23:26 ` Russell King - ARM Linux
2018-04-26 9:17 ` Daniel Vetter
2018-04-26 9:09 ` Christoph Hellwig
2018-04-26 9:45 ` Daniel Vetter
2018-04-26 11:12 ` Russell King - ARM Linux
2018-04-25 22:54 ` Russell King - ARM Linux
2018-04-26 9:13 ` Christoph Hellwig
2018-04-26 9:20 ` [Linaro-mm-sig] " Daniel Vetter
2018-04-26 9:24 ` Christoph Hellwig
2018-04-26 9:39 ` Daniel Vetter
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=20180425085439.GA29996@infradead.org \
--to=hch@infradead.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).