From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/4] accel/ivpu: Use GEM shmem
Date: Wed, 8 Nov 2023 16:30:46 +0100 [thread overview]
Message-ID: <31be3576-d7df-46f1-975e-2e7e9800efa4@linux.intel.com> (raw)
In-Reply-To: <20231031073156.1301669-1-stanislaw.gruszka@linux.intel.com>
Applied to drm-misc-next
On 31.10.2023 08:31, Stanislaw Gruszka wrote:
> Use GEM shmem for buffer management code;
>
> Previously sent as RFC:
> https://lore.kernel.org/dri-devel/20230901164842.178654-1-stanislaw.gruszka@linux.intel.com/
>
> Compared to RFC only changelog's were improved.
>
> Jacek Lawrynowicz (4):
> accel/ivpu: Allocate vpu_addr in gem->open() callback
> accel/ivpu: Fix locking in ivpu_bo_remove_all_bos_from_context()
> accel/ivpu: Remove support for uncached buffers
> accel/ivpu: Use GEM shmem helper for all buffers
>
> drivers/accel/ivpu/Kconfig | 2 +-
> drivers/accel/ivpu/ivpu_drv.c | 13 +-
> drivers/accel/ivpu/ivpu_drv.h | 3 +
> drivers/accel/ivpu/ivpu_fw.c | 2 +-
> drivers/accel/ivpu/ivpu_gem.c | 678 ++++++++------------------
> drivers/accel/ivpu/ivpu_gem.h | 75 +--
> drivers/accel/ivpu/ivpu_job.c | 8 +-
> drivers/accel/ivpu/ivpu_mmu.c | 5 +-
> drivers/accel/ivpu/ivpu_mmu_context.c | 38 +-
> drivers/accel/ivpu/ivpu_mmu_context.h | 11 +-
> include/uapi/drm/ivpu_accel.h | 2 +-
> 11 files changed, 266 insertions(+), 571 deletions(-)
>
prev parent reply other threads:[~2023-11-08 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 7:31 [PATCH 0/4] accel/ivpu: Use GEM shmem Stanislaw Gruszka
2023-10-31 7:31 ` [PATCH 1/4] accel/ivpu: Allocate vpu_addr in gem->open() callback Stanislaw Gruszka
2023-10-31 7:31 ` [PATCH 2/4] accel/ivpu: Fix locking in ivpu_bo_remove_all_bos_from_context() Stanislaw Gruszka
2023-10-31 7:31 ` [PATCH 3/4] accel/ivpu: Remove support for uncached buffers Stanislaw Gruszka
2023-10-31 7:31 ` [PATCH 4/4] accel/ivpu: Use GEM shmem helper for all buffers Stanislaw Gruszka
2023-11-08 15:30 ` Jacek Lawrynowicz [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=31be3576-d7df-46f1-975e-2e7e9800efa4@linux.intel.com \
--to=jacek.lawrynowicz@linux.intel.com \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.