From: Thomas Hellstrom <thellstrom@vmware.com>
To: "hch@lst.de" <hch@lst.de>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Deepak Singh Rawat <drawat@vmware.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>
Subject: Re: revert dma direct internals abuse
Date: Tue, 23 Apr 2019 12:26:05 +0000 [thread overview]
Message-ID: <a5643cb106797f7079c70d63f5031bdc01259bb0.camel@vmware.com> (raw)
In-Reply-To: <20190422175623.GA32411@lst.de>
Hi, Christoph,
On Mon, 2019-04-22 at 19:56 +0200, hch@lst.de wrote:
> On Wed, Apr 10, 2019 at 03:01:14PM +0000, Thomas Hellstrom wrote:
> > > So can you please respin a version acceptable to you and submit
> > > it
> > > for 5.1 ASAP? Otherwise I'll need to move ahead with the simple
> > > revert.
> >
> > I will.
> > I need to do some testing to investigate how to best choose between
> > the
> > options, but will have something ready for 5.1.
>
> I still don't see anything in -rc6..
Been on easter vacation. I have a patch ready for review, though, will
send it out in a moment.
It turns out that to do something well-behaved in case someone sets
swiotlb=force, the variable swiotlb_force would need to be exported.
(I can't rely on swiotlb_nr_tbl()).
That's not currently done in the patch, but instead the driver just
malfunctions like most other graphics drivers.
/Thomas
prev parent reply other threads:[~2019-04-23 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 10:55 Christoph Hellwig
2019-04-08 10:55 ` [PATCH] Revert "drm/vmwgfx: Improve on IOMMU detection" Christoph Hellwig
2019-04-08 20:05 ` Thomas Hellstrom
2019-04-08 18:47 ` revert dma direct internals abuse Thomas Hellstrom
2019-04-09 9:57 ` hch
2019-04-09 13:04 ` Thomas Hellstrom
2019-04-09 13:31 ` hch
2019-04-09 14:17 ` Thomas Hellstrom
2019-04-09 15:25 ` hch
2019-04-09 17:24 ` Thomas Hellstrom
2019-04-10 6:43 ` hch
2019-04-10 15:01 ` Thomas Hellstrom
2019-04-22 17:56 ` hch
2019-04-23 12:26 ` Thomas Hellstrom [this message]
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=a5643cb106797f7079c70d63f5031bdc01259bb0.camel@vmware.com \
--to=thellstrom@vmware.com \
--cc=drawat@vmware.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome