intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	Jani Nikula <jani.nikula@intel.com>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>
Subject: [Intel-gfx] [PULL] gvt-next-fixes
Date: Fri, 28 Apr 2023 15:47:55 +0800	[thread overview]
Message-ID: <ZEt6K2C0WJTePdk6@debian-scheme> (raw)

[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]


Hi,

Here's one single change for gvt to use idr based dmabuf object
reference instead of old adhoc code. We've verified no regression
for internal test.

Thanks.
--
The following changes since commit d944eafed618a8507270b324ad9d5405bb7f0b3e:

  drm/i915: Check pipe source size when using skl+ scalers (2023-04-24 14:48:42 +0300)

are available in the Git repository at:

  https://github.com/intel/gvt-linux.git tags/gvt-next-fixes-2023-04-28

for you to fetch changes up to 004040fdb55fa55463730c95d1384cb67f9396c3:

  drm/i915/gvt: Make use of idr_find and idr_for_each_entry in dmabuf (2023-04-28 15:21:17 +0800)

----------------------------------------------------------------
gvt-next-fixes-2023-04-28

- Use idr based dmabuf object reference (Cai Huoqing)

----------------------------------------------------------------
Cai Huoqing (1):
      drm/i915/gvt: Make use of idr_find and idr_for_each_entry in dmabuf

 drivers/gpu/drm/i915/gvt/dmabuf.c | 58 ++++++++-------------------------------
 drivers/gpu/drm/i915/gvt/dmabuf.h |  1 -
 drivers/gpu/drm/i915/gvt/gvt.h    |  1 -
 drivers/gpu/drm/i915/gvt/vgpu.c   |  1 -
 4 files changed, 12 insertions(+), 49 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

             reply	other threads:[~2023-04-28  7:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28  7:47 Zhenyu Wang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-23  8:50 [Intel-gfx] [PULL] gvt-next-fixes Zhenyu Wang
2023-02-23 12:11 ` Jani Nikula
2021-04-29  8:51 Zhenyu Wang
2021-04-29 11:12 ` Jani Nikula
2021-04-21  9:45 Zhenyu Wang
2021-04-21 10:51 ` Jani Nikula
2021-02-22  8:34 Zhenyu Wang
2021-02-23 14:42 ` Rodrigo Vivi
2020-12-25  2:20 Zhenyu Wang
2021-01-05  7:54 ` Zhenyu Wang
2021-01-05  8:36   ` Jani Nikula
2021-01-05 20:44     ` Rodrigo Vivi
2020-08-05  8:02 Zhenyu Wang
2020-08-06 15:17 ` Jani Nikula
2020-05-28  3:35 Zhenyu Wang
2020-06-02 14:04 ` Joonas Lahtinen
2020-03-31  7:00 Zhenyu Wang
2020-03-31 16:26 ` Rodrigo Vivi
2020-04-03  3:05   ` Zhenyu Wang
2020-04-03 17:50     ` Rodrigo Vivi
2020-04-07  8:02       ` Zhenyu Wang
2020-04-07 13:35         ` Rodrigo Vivi
2020-04-07 13:53           ` Jani Nikula
2020-04-07 23:36             ` Zhenyu Wang
2019-12-02  5:17 Zhenyu Wang
2019-12-02  5:17 ` [Intel-gfx] " Zhenyu Wang
2019-12-05  6:11 ` Zhenyu Wang
2019-12-05  8:14   ` Joonas Lahtinen
2019-12-05  8:49     ` Zhenyu Wang
2019-11-12  6:20 Zhenyu Wang
2019-11-12  6:20 ` [Intel-gfx] " Zhenyu Wang
2019-11-20 11:25 ` Joonas Lahtinen
2019-11-20 11:25   ` [Intel-gfx] " Joonas Lahtinen

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=ZEt6K2C0WJTePdk6@debian-scheme \
    --to=zhenyuw@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=tvrtko.ursulin@linux.intel.com \
    --cc=zhiyuan.lv@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;
as well as URLs for NNTP newsgroup(s).