From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"Steven Price" <steven.price@arm.com>,
"Liviu Dudau" <liviu.dudau@arm.com>
Cc: kernel@collabora.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [RFC PATCH v2 3/6] drm/shmem: Implement sparse allocation of pages for shmem objects
Date: Wed, 26 Mar 2025 22:54:27 +0300 [thread overview]
Message-ID: <e4f41400-b300-43ee-843f-8bc407aa9f76@collabora.com> (raw)
In-Reply-To: <20250326021433.772196-4-adrian.larumbe@collabora.com>
On 3/26/25 05:14, Adrián Larumbe wrote:
> +static struct sg_table *
> +drm_gem_shmem_sparse_get_sgt_range(struct drm_gem_shmem_object *shmem,
> + unsigned int n_pages, pgoff_t page_offset,
> + gfp_t gfp)
> +{
> + struct drm_gem_object *obj = &shmem->base;
> + struct sg_table *sgt;
> + int ret;
> +
> + if (drm_WARN_ON(obj->dev, !shmem->sparse))
> + return ERR_PTR(-EINVAL);
> +
> + /* If the page range wasn't allocated, then bail out immediately */
> + if (xa_load(&shmem->xapages, page_offset) == NULL)
> + return ERR_PTR(-EINVAL);
> +
> + sgt = kzalloc(sizeof(*sgt), GFP_NOWAIT);
You likely meant to use the gfp arg here.
--
Best regards,
Dmitry
next prev parent reply other threads:[~2025-03-26 19:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 2:14 [RFC PATCH v2 0/6] Introduce sparse DRM shmem object allocations Adrián Larumbe
2025-03-26 2:14 ` [RFC PATCH v2 1/6] lib/scatterlist.c: Support constructing sgt from page xarray Adrián Larumbe
2025-04-01 8:28 ` Boris Brezillon
2025-03-26 2:14 ` [RFC PATCH v2 2/6] drm/shmem: Introduce the notion of sparse objects Adrián Larumbe
2025-04-01 8:45 ` Boris Brezillon
2025-03-26 2:14 ` [RFC PATCH v2 3/6] drm/shmem: Implement sparse allocation of pages for shmem objects Adrián Larumbe
2025-03-26 19:54 ` Dmitry Osipenko [this message]
2025-04-01 9:36 ` Boris Brezillon
2025-03-26 2:14 ` [RFC PATCH v2 4/6] drm/panfrost: Use shmem sparse allocation for heap BOs Adrián Larumbe
2025-03-26 2:14 ` [RFC PATCH v2 5/6] drm/shmem: Add a helper to check object's page backing status Adrián Larumbe
2025-03-31 7:15 ` Thomas Zimmermann
2025-03-26 2:14 ` [RFC PATCH v2 6/6] drm/panfrost/panthor: Take sparse objects into account for fdinfo Adrián Larumbe
2025-04-01 9:39 ` Boris Brezillon
2025-03-31 7:13 ` [RFC PATCH v2 0/6] Introduce sparse DRM shmem object allocations Thomas Zimmermann
2025-03-31 8:31 ` Boris Brezillon
2025-03-31 9:12 ` Thomas Zimmermann
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=e4f41400-b300-43ee-843f-8bc407aa9f76@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--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
all inboxes | Powered by JetHome®