From: "Jürgen Groß" <jgross@suse.com>
To: Lin Liu <lin.liu01@citrix.com>, sstabellini@kernel.org
Cc: oleksandr_tyshchenko@epam.com, andrew.cooper3@citrix.com,
ross.lagerwall@citrix.com, xen-devel@lists.xenproject.org,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] xen/swiotlb: Bounce mappings that cross the segment boundary
Date: Thu, 19 Nov 2026 07:44:54 +0100 [thread overview]
Message-ID: <c906fcbd-8671-4257-8250-9c09d38f6b53@suse.com> (raw)
In-Reply-To: <4a2d59f8d5a2b1399fc8bdf6e49202c9c2f394a7.1795069501.git.lin.liu01@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 774 bytes --]
On 19.11.26 07:38, Lin Liu wrote:
> The block layer applies a device's DMA segment boundary to
> pseudo-physical addresses, but in a Xen PV domain the bus address is the
> machine address. A segment that is contiguous in both spaces can still
> cross the boundary in machine space and reach the device. AHCI declares
> a 4 GiB boundary, and controllers that do not carry across it (e.g.
> Marvell 88SE9230) then DMA the tail of the transfer 4 GiB too low.
>
> Bounce such streaming mappings. Coherent allocations need no check:
> they are naturally aligned in bus space (range_requires_alignment()), so
> they cannot cross a boundary they fit in.
>
> Signed-off-by: Lin Liu <lin.liu01@citrix.com>
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2026-11-19 6:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 12:47 [PATCH] xen/swiotlb: Check the segment boundary in range_straddles_page_boundary() Lin Liu
2026-11-18 11:25 ` Ross Lagerwall
2026-11-18 12:24 ` Jürgen Groß
2026-11-19 4:35 ` Lin Liu
2026-11-19 5:59 ` Jürgen Groß
2026-11-19 6:12 ` Lin Liu
2026-11-19 6:38 ` [PATCH v2] xen/swiotlb: Bounce mappings that cross the segment boundary Lin Liu
2026-11-19 6:44 ` Jürgen Groß [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=c906fcbd-8671-4257-8250-9c09d38f6b53@suse.com \
--to=jgross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=iommu@lists.linux.dev \
--cc=lin.liu01@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=ross.lagerwall@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®