From: Alex Deucher <alexdeucher@gmail.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
linux-samsung-soc@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
David Airlie <airlied@linux.ie>,
Shane Francis <bigbeeshane@gmail.com>,
"Michael J . Ruhl" <michael.j.ruhl@intel.com>,
"for 3.8" <stable@vger.kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH v2] drm/prime: fix extracting of the DMA addresses from a scatterlist
Date: Sun, 5 Apr 2020 10:47:49 -0400 [thread overview]
Message-ID: <CADnq5_NpHvmRvzvh1aF293UDUXiHF4Dg1rRNkt7XbM_VB98JCg@mail.gmail.com> (raw)
In-Reply-To: <20200327162126.29705-1-m.szyprowski@samsung.com>
On Fri, Mar 27, 2020 at 12:23 PM Marek Szyprowski
<m.szyprowski@samsung.com> wrote:
>
> Scatterlist elements contains both pages and DMA addresses, but one
> should not assume 1:1 relation between them. The sg->length is the size
> of the physical memory chunk described by the sg->page, while
> sg_dma_len(sg) is the size of the DMA (IO virtual) chunk described by
> the sg_dma_address(sg).
>
> The proper way of extracting both: pages and DMA addresses of the whole
> buffer described by a scatterlist it to iterate independently over the
> sg->pages/sg->length and sg_dma_address(sg)/sg_dma_len(sg) entries.
>
> Fixes: 42e67b479eab ("drm/prime: use dma length macro when mapping sg")
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Applied. Thanks and sorry for the breakage.
Alex
> ---
> drivers/gpu/drm/drm_prime.c | 37 +++++++++++++++++++++++++------------
> 1 file changed, 25 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c
> index 1de2cde2277c..282774e469ac 100644
> --- a/drivers/gpu/drm/drm_prime.c
> +++ b/drivers/gpu/drm/drm_prime.c
> @@ -962,27 +962,40 @@ int drm_prime_sg_to_page_addr_arrays(struct sg_table *sgt, struct page **pages,
> unsigned count;
> struct scatterlist *sg;
> struct page *page;
> - u32 len, index;
> + u32 page_len, page_index;
> dma_addr_t addr;
> + u32 dma_len, dma_index;
>
> - index = 0;
> + /*
> + * Scatterlist elements contains both pages and DMA addresses, but
> + * one shoud not assume 1:1 relation between them. The sg->length is
> + * the size of the physical memory chunk described by the sg->page,
> + * while sg_dma_len(sg) is the size of the DMA (IO virtual) chunk
> + * described by the sg_dma_address(sg).
> + */
> + page_index = 0;
> + dma_index = 0;
> for_each_sg(sgt->sgl, sg, sgt->nents, count) {
> - len = sg_dma_len(sg);
> + page_len = sg->length;
> page = sg_page(sg);
> + dma_len = sg_dma_len(sg);
> addr = sg_dma_address(sg);
>
> - while (len > 0) {
> - if (WARN_ON(index >= max_entries))
> + while (pages && page_len > 0) {
> + if (WARN_ON(page_index >= max_entries))
> return -1;
> - if (pages)
> - pages[index] = page;
> - if (addrs)
> - addrs[index] = addr;
> -
> + pages[page_index] = page;
> page++;
> + page_len -= PAGE_SIZE;
> + page_index++;
> + }
> + while (addrs && dma_len > 0) {
> + if (WARN_ON(dma_index >= max_entries))
> + return -1;
> + addrs[dma_index] = addr;
> addr += PAGE_SIZE;
> - len -= PAGE_SIZE;
> - index++;
> + dma_len -= PAGE_SIZE;
> + dma_index++;
> }
> }
> return 0;
> --
> 2.17.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-04-05 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200327162330eucas1p1b0413e0e9887aa76d3048f86d2166dcd@eucas1p1.samsung.com>
2020-03-27 16:21 ` [PATCH v2] drm/prime: fix extracting of the DMA addresses from a scatterlist Marek Szyprowski
2020-03-27 18:31 ` Ruhl, Michael J
2020-03-28 18:36 ` Shane Francis
2020-03-29 9:55 ` Marek Szyprowski
2020-03-30 13:10 ` Robin Murphy
2020-03-30 13:46 ` Ruhl, Michael J
2020-03-28 7:18 ` Greg KH
2020-04-05 14:47 ` Alex Deucher [this message]
2020-04-05 16:40 ` Greg KH
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=CADnq5_NpHvmRvzvh1aF293UDUXiHF4Dg1rRNkt7XbM_VB98JCg@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=b.zolnierkie@samsung.com \
--cc=bigbeeshane@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=michael.j.ruhl@intel.com \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).