All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>
Cc: Oded Gabbay <ogabbay@kernel.org>,
	Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [RFC 1/4] accel/ivpu: Allocate vpu_addr in gem->open() callback
Date: Tue, 19 Sep 2023 11:24:59 +0200	[thread overview]
Message-ID: <20230919092459.GA563961@linux.intel.com> (raw)
In-Reply-To: <62e3769d-b747-9258-c330-97c034ea52ec@quicinc.com>

On Mon, Sep 11, 2023 at 09:19:03AM -0600, Jeffrey Hugo wrote:
> On 9/1/2023 10:48 AM, Stanislaw Gruszka wrote:
> > From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
> > 
> > gem->open() is called during handle creation for a gem object.
> > It is called during prime import and in BO_CREATE ioctl.
> 
> I feel like the "why" is missing.  This appears to start to explain how
> gem->open() might be useful for the driver, but does not seem to complete
> explaining the connection to the driver.  From the code changes, it looks
> like using gem->open() simplifies the code by allocating the vpu_addr in one
> place for all BOs.  If that is the goal, I feel that it should be mentioned
> here.

I'm going to change to:

Use gem->open() callback to simplify the code and prepare for gem_shmem
conversion. It is called during handle creation for a gem object - during
prime import and in BO_CREATE ioctl. Hence can be used for vpu_addr
allocation. On the way remove unused bo->user_ptr field.


Regards
Stanislaw

  reply	other threads:[~2023-09-19  9:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01 16:48 [RFC 0/4] accel/ivpu: Use GEM shmem Stanislaw Gruszka
2023-09-01 16:48 ` [RFC 1/4] accel/ivpu: Allocate vpu_addr in gem->open() callback Stanislaw Gruszka
2023-09-11 15:19   ` Jeffrey Hugo
2023-09-19  9:24     ` Stanislaw Gruszka [this message]
2023-09-22 15:20       ` Jeffrey Hugo
2023-09-01 16:48 ` [RFC 2/4] accel/ivpu: Fix locking in ivpu_bo_remove_all_bos_from_context() Stanislaw Gruszka
2023-09-11 15:21   ` Jeffrey Hugo
2023-09-01 16:48 ` [RFC 3/4] accel/ivpu: Remove support for uncached buffers Stanislaw Gruszka
2023-09-11 15:24   ` Jeffrey Hugo
2023-09-19  9:49     ` Stanislaw Gruszka
2023-09-22 15:21       ` Jeffrey Hugo
2023-09-01 16:48 ` [RFC 4/4] accel/ivpu: Use GEM shmem helper for all buffers Stanislaw Gruszka
2023-09-11 15:27   ` Jeffrey Hugo

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=20230919092459.GA563961@linux.intel.com \
    --to=stanislaw.gruszka@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jacek.lawrynowicz@linux.intel.com \
    --cc=ogabbay@kernel.org \
    --cc=quic_jhugo@quicinc.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 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.