From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/4] drm/i915/guc: add a helper to allocate and map guc vma
Date: Thu, 07 Nov 2019 08:19:30 +0000 [thread overview]
Message-ID: <157311477091.26738.14422714394668638981@skylake-alporthouse-com> (raw)
In-Reply-To: <20191106222550.20752-3-daniele.ceraolospurio@intel.com>
Quoting Daniele Ceraolo Spurio (2019-11-06 22:25:48)
> We already have a couple of use-cases in the code and another one will
> come in one of the later patches in the series.
>
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/4] drm/i915/guc: add a helper to allocate and map guc vma
Date: Thu, 07 Nov 2019 08:19:30 +0000 [thread overview]
Message-ID: <157311477091.26738.14422714394668638981@skylake-alporthouse-com> (raw)
Message-ID: <20191107081930.M5DRGsuwaeTaHFyhldjIV6bRCP8xjw4X3az7KruYvdg@z> (raw)
In-Reply-To: <20191106222550.20752-3-daniele.ceraolospurio@intel.com>
Quoting Daniele Ceraolo Spurio (2019-11-06 22:25:48)
> We already have a couple of use-cases in the code and another one will
> come in one of the later patches in the series.
>
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-07 8:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 22:25 [PATCH 0/4] Start removing legacy guc code Daniele Ceraolo Spurio
2019-11-06 22:25 ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-11-06 22:25 ` [PATCH 1/4] drm/i915/guc: Drop leftover preemption code Daniele Ceraolo Spurio
2019-11-06 22:25 ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-11-07 8:17 ` Chris Wilson
2019-11-07 8:17 ` [Intel-gfx] " Chris Wilson
2019-11-06 22:25 ` [PATCH 2/4] drm/i915/guc: add a helper to allocate and map guc vma Daniele Ceraolo Spurio
2019-11-06 22:25 ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-11-07 8:19 ` Chris Wilson [this message]
2019-11-07 8:19 ` Chris Wilson
2019-11-06 22:25 ` [PATCH 3/4] drm/i915/guc: kill doorbell code and selftests Daniele Ceraolo Spurio
2019-11-06 22:25 ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-11-14 23:56 ` John Harrison
2019-11-14 23:56 ` [Intel-gfx] " John Harrison
2019-11-18 22:20 ` Daniele Ceraolo Spurio
2019-11-18 22:20 ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-11-06 22:25 ` [PATCH 4/4] drm/i915/guc: kill the GuC client Daniele Ceraolo Spurio
2019-11-06 22:25 ` [Intel-gfx] " Daniele Ceraolo Spurio
2019-11-15 0:22 ` John Harrison
2019-11-15 0:22 ` [Intel-gfx] " John Harrison
2019-11-07 0:52 ` ✗ Fi.CI.CHECKPATCH: warning for Start removing legacy guc code Patchwork
2019-11-07 0:52 ` [Intel-gfx] " Patchwork
2019-11-07 1:08 ` ✗ Fi.CI.DOCS: " Patchwork
2019-11-07 1:08 ` [Intel-gfx] " Patchwork
2019-11-07 1:15 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-07 1:15 ` [Intel-gfx] " Patchwork
2019-11-08 4:36 ` ✓ Fi.CI.IGT: " Patchwork
2019-11-08 4:36 ` [Intel-gfx] " 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=157311477091.26738.14422714394668638981@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-gfx@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.