From: Kenneth Graunke <kenneth.w.graunke@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Brost, Matthew" <matthew.brost@intel.com>,
"Souza, Jose" <jose.souza@intel.com>
Cc: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] drm/xe: Use bookkeep slots for external BO's in exec IOCTL
Date: Wed, 11 Sep 2024 15:06:40 -0700 [thread overview]
Message-ID: <5030690.31r3eYUQgx@imeretto> (raw)
In-Reply-To: <7199ce6364bc4ae5d66600e49acb288fa58a585e.camel@intel.com>
On Wednesday, September 11, 2024 8:37:11 AM PDT Souza, Jose wrote:
> On Wed, 2024-09-11 at 08:26 -0700, Matthew Brost wrote:
>
> > Fix external BO's dma-resv usage in exec IOCTL using bookkeep slots
> > rather than write slots. This leaves syncing to user space rather than
> > the KMD blindly enforcing write semantics on every external BO.
> >
>
>
> Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
next prev parent reply other threads:[~2024-09-11 22:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 15:26 [PATCH] drm/xe: Use bookkeep slots for external BO's in exec IOCTL Matthew Brost
2024-09-11 15:31 ` ✓ CI.Patch_applied: success for " Patchwork
2024-09-11 15:31 ` ✓ CI.checkpatch: " Patchwork
2024-09-11 15:32 ` ✓ CI.KUnit: " Patchwork
2024-09-11 15:37 ` [PATCH] " Souza, Jose
2024-09-11 22:06 ` Kenneth Graunke [this message]
2024-09-11 15:44 ` ✓ CI.Build: success for " Patchwork
2024-09-11 15:46 ` ✓ CI.Hooks: " Patchwork
2024-09-11 15:48 ` ✓ CI.checksparse: " Patchwork
2024-09-11 16:04 ` ✗ CI.BAT: failure " Patchwork
2024-09-11 16:45 ` Matthew Brost
2024-09-11 17:06 ` ✗ CI.FULL: " Patchwork
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=5030690.31r3eYUQgx@imeretto \
--to=kenneth.w.graunke@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=matthew.brost@intel.com \
--cc=paulo.r.zanoni@intel.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