From: Andrew Morton <akpm@linux-foundation.org>
To: Pantelis Antoniou <p.antoniou@partner.samsung.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Artem Krupotkin <artem.k@samsung.com>,
Charles Briere <c.briere@samsung.com>,
Wade Farnsworth <wade.farnsworth@siemens.com>
Subject: Re: [PATCH 0/1] Fix zero copy I/O on __get_user_pages allocated pages
Date: Wed, 7 May 2025 14:54:02 -0700 [thread overview]
Message-ID: <20250507145402.d162d92fa29130d690461a0b@linux-foundation.org> (raw)
In-Reply-To: <20250507154105.763088-1-p.antoniou@partner.samsung.com>
On Wed, 7 May 2025 10:41:04 -0500 Pantelis Antoniou <p.antoniou@partner.samsung.com> wrote:
> One example of that is the 9p filesystem which is commonly used in qemu
> based setups for sharing files with the host.
>
> In our emulation environment we have noticed failing writes when performing
> I/O from a userspace mapped DRM GEM buffer object.
> The platform does not use VRAM, all graphics memory is regular DRAM memory,
> allocated via __get_free_pages
>
> The same write was successful from a heap allocated bounce buffer.
>
> The sequence of events is as follows.
>
> ..
>
There's a lot of good stuff in this [0/N], but a single patch "series"
is cumbersome. Can you please redo this as a standalone patch in which
the changelog is the union of [0/1] and [1/1]?
prev parent reply other threads:[~2025-05-07 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250507154119uscas1p2a4055d14ab111fdb94a6378789c38d9d@uscas1p2.samsung.com>
2025-05-07 15:41 ` Pantelis Antoniou
[not found] ` <CGME20250507154119uscas1p17799fe7589e4f1bd53d2d3dc7f44cb8c@uscas1p1.samsung.com>
2025-05-07 15:41 ` [PATCH 1/1] " Pantelis Antoniou
2025-05-08 15:03 ` David Hildenbrand
2025-05-08 15:23 ` Pantelis Antoniou
2025-05-08 15:37 ` David Hildenbrand
2025-05-08 15:47 ` Pantelis Antoniou
2025-05-07 21:50 ` [PATCH 0/1] " Andrew Morton
2025-05-08 8:24 ` Pantelis Antoniou
2025-05-07 21:54 ` Andrew Morton [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=20250507145402.d162d92fa29130d690461a0b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=artem.k@samsung.com \
--cc=c.briere@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=p.antoniou@partner.samsung.com \
--cc=wade.farnsworth@siemens.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