From: Thomas Hellstrom <thellstrom@vmware.com>
To: hch@lst.de, dri-devel@lists.freedesktop.org,
linux-graphics-maintainer@vmware.com
Subject: [PATCH 3/4] drm/vmwgfx: fix the check when to use dma_alloc_coherent
Date: Fri, 25 Jan 2019 09:12:14 +0100 [thread overview]
Message-ID: <20190125081215.4622-4-thellstrom@vmware.com> (raw)
In-Reply-To: <20190125081215.4622-1-thellstrom@vmware.com>
From: Christoph Hellwig <hch@lst.de>
Since Linux 4.21 we merged the swiotlb ops into the DMA direct ops,
so they would always have a the sync_single methods. But late in
the cicle we also removed the direct ops entirely, so we'd see NULL
DMA ops. Switch vmw_dma_select_mode to only detect swiotlb presence
using swiotlb_nr_tbl() instead.
Fixes: 55897af630 ("dma-direct: merge swiotlb_dma_ops into the dma_direct code")
Fixes: 356da6d0cd ("dma-mapping: bypass indirect calls for dma-direct")
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 11 ++++-------
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
index b7777b5b4a81..1456101e67a9 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
@@ -565,7 +565,6 @@ static int vmw_dma_select_mode(struct vmw_private *dev_priv)
[vmw_dma_alloc_coherent] = "Using coherent TTM pages.",
[vmw_dma_map_populate] = "Keeping DMA mappings.",
[vmw_dma_map_bind] = "Giving up DMA mappings early."};
- const struct dma_map_ops *dma_ops = get_dma_ops(dev_priv->dev->dev);
if (intel_iommu_enabled) {
dev_priv->map_mode = vmw_dma_map_populate;
@@ -578,14 +577,12 @@ static int vmw_dma_select_mode(struct vmw_private *dev_priv)
return 0;
}
- dev_priv->map_mode = vmw_dma_map_populate;
-
- if (dma_ops && dma_ops->sync_single_for_cpu)
- dev_priv->map_mode = vmw_dma_alloc_coherent;
#ifdef CONFIG_SWIOTLB
- if (swiotlb_nr_tbl() == 0)
- dev_priv->map_mode = vmw_dma_map_populate;
+ if (swiotlb_nr_tbl())
+ dev_priv->map_mode = vmw_dma_alloc_coherent;
+ else
#endif
+ dev_priv->map_mode = vmw_dma_map_populate;
out_fixup:
if (dev_priv->map_mode == vmw_dma_map_populate &&
--
2.19.0.rc1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-01-25 8:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 8:12 [PATCH 0/4] Fix DMA ops layering violations in vmwgfx v2 Thomas Hellstrom
2019-01-25 8:12 ` [PATCH 1/4] drm/vmwgfx: remove CONFIG_X86 ifdefs Thomas Hellstrom
2019-01-25 8:12 ` [PATCH 2/4] drm/vmwgfx: remove CONFIG_INTEL_IOMMU ifdefs v2 Thomas Hellstrom
[not found] ` <20190204081932.GB5730@lst.de>
2019-02-04 12:11 ` Thomas Hellstrom
2019-02-05 7:59 ` Thomas Hellstrom
2019-02-05 8:01 ` hch
2019-01-25 8:12 ` Thomas Hellstrom [this message]
2019-01-25 8:12 ` [PATCH 4/4] drm/vmwgfx: unwind spaghetti code in vmw_dma_select_mode Thomas Hellstrom
-- strict thread matches above, loose matches on Subject: below --
2019-01-05 8:01 fix DMA ops layering violations in vmwgfx Christoph Hellwig
2019-01-05 8:01 ` [PATCH 3/4] drm/vmwgfx: fix the check when to use dma_alloc_coherent Christoph Hellwig
2019-01-05 8:01 ` Christoph Hellwig
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=20190125081215.4622-4-thellstrom@vmware.com \
--to=thellstrom@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=linux-graphics-maintainer@vmware.com \
/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.