From: Thomas Hellstrom <thellstrom@vmware.com>
To: hch@lst.de, dri-devel@lists.freedesktop.org,
linux-graphics-maintainer@vmware.com
Subject: [PATCH 0/4] Fix DMA ops layering violations in vmwgfx v2
Date: Fri, 25 Jan 2019 09:12:11 +0100 [thread overview]
Message-ID: <20190125081215.4622-1-thellstrom@vmware.com> (raw)
This is a patch set from Christoph Hellwig. Patch 2 has been updated by
me to not remove checks for TTM coherent pool presence. Ideally, we
should query TTM for this instead and I'll have a patch set intended for
5.1 so that we can do that. But I don't want to introduce cross-module API
additions outside of a merge window.
Original patch set description:
vmwgfx has been doing some odd checks based on DMA ops which rely
on deep DMA mapping layer internals, and I think the changes in
Linux 4.21 finally broke most of these implicit assumptions.
The real fix is in patch 3, but I think the others are important
to make it clear what is actually going on.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-01-25 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 8:12 Thomas Hellstrom [this message]
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-01-25 8:12 ` [PATCH 3/4] drm/vmwgfx: fix the check when to use dma_alloc_coherent Thomas Hellstrom
2019-01-25 8:12 ` [PATCH 4/4] drm/vmwgfx: unwind spaghetti code in vmw_dma_select_mode Thomas Hellstrom
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-1-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox