From: Christoph Hellwig <hch@lst.de>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Leon Romanovsky <leon@kernel.org>,
m.szyprowski@samsung.com, hch@lst.de, robin.murphy@arm.com,
djbw@kernel.org, akpm@linux-foundation.org,
catalin.marinas@arm.com, harry@kernel.org, ming.lei@redhat.com,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] dma-debug: skip cacheline overlap tracking on cache-coherent architectures
Date: Tue, 19 May 2026 09:17:58 +0200 [thread overview]
Message-ID: <20260519071758.GB10037@lst.de> (raw)
In-Reply-To: <CABXGCsMA+uZtoup+QtGsPQcyF6TZimxYFOR2sDQksNkLpJq+2g@mail.gmail.com>
On Mon, May 18, 2026 at 06:29:11PM +0500, Mikhail Gavrilov wrote:
> DIO from userspace is unfixable from the kernel side per that
> message; raid1 acknowledged as needing a fix Christoph didn't have.
> Two years on, those cases (plus dm-thin and io_uring polled tests
> from Ming Lei's report) still don't have an annotation path. This
> patch covers what annotation can't reach without preventing future
> annotation work.
It is not. We could require direct I/O to/from devices that are
attached without DMA coherence to require cache line alignment.
Now that Keith pushed down the checking into the driver that's even
fairly easily doable.
next prev parent reply other threads:[~2026-05-19 7:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 11:32 [PATCH] dma-debug: skip cacheline overlap tracking on cache-coherent architectures Mikhail Gavrilov
2026-05-18 12:10 ` Leon Romanovsky
2026-05-18 12:23 ` Mikhail Gavrilov
2026-05-18 12:53 ` Leon Romanovsky
2026-05-18 13:29 ` Mikhail Gavrilov
2026-05-19 7:17 ` Christoph Hellwig [this message]
2026-05-19 8:03 ` Mikhail Gavrilov
2026-05-19 9:28 ` Christoph Hellwig
2026-05-19 9:57 ` Mikhail Gavrilov
2026-05-19 11:49 ` Christoph Hellwig
2026-05-19 9:06 ` David Laight
2026-05-19 9:18 ` Mikhail Gavrilov
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=20260519071758.GB10037@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=djbw@kernel.org \
--cc=harry@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=kbusch@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=ming.lei@redhat.com \
--cc=robin.murphy@arm.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