From: Anshuman Gupta <anshuman.gupta@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: matthew.auld@intel.com, rodrigo.vivi@intel.com
Subject: [Intel-gfx] [RFC 0/1] DGFX pin_map with rpm
Date: Thu, 15 Sep 2022 16:03:10 +0530 [thread overview]
Message-ID: <20220915103311.5634-1-anshuman.gupta@intel.com> (raw)
As per PCIe Spec Section 5.3.1.4.1
When a PCIe function is in d3hot state,
Configuration and Message requests are the only TLPs accepted by a
Function in the D3hot state. All other received Requests must be
handled as Unsupported Requests, and all received Completions
may optionally be handled as Unexpected Completions.
Therefore all PCIe iomem transaction requires to keep the PCIe endpoint
function in D0 state.
This RFC proposal is depends on the assumption with my understanding of code,
we can't partially pin_map the lmem gem object, with considering
that every caller of i915_gem_onject_pin_map() does not need to grab
the wakeref. We can embedded the wakeref inside the gem object itself.
Requesting community to provide the feedback on this proposal.
Anshuman Gupta (1):
drm/i915/dgfx: Handling of pin_map against rpm
drivers/gpu/drm/i915/gem/i915_gem_object.c | 2 ++
drivers/gpu/drm/i915/gem/i915_gem_object.h | 5 +++++
drivers/gpu/drm/i915/gem/i915_gem_object_types.h | 14 ++++++++++++++
drivers/gpu/drm/i915/gem/i915_gem_pages.c | 8 ++++++++
4 files changed, 29 insertions(+)
--
2.26.2
next reply other threads:[~2022-09-15 10:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 10:33 Anshuman Gupta [this message]
2022-09-15 10:33 ` [Intel-gfx] [RFC 1/1] drm/i915/dgfx: Handling of pin_map against rpm Anshuman Gupta
2022-09-15 14:17 ` Tvrtko Ursulin
2022-09-15 16:49 ` Gupta, Anshuman
2022-09-15 14:32 ` Tvrtko Ursulin
2022-09-15 16:41 ` Gupta, Anshuman
2022-09-15 17:07 ` Tvrtko Ursulin
2022-09-16 10:30 ` Gupta, Anshuman
2022-09-16 10:48 ` Tvrtko Ursulin
2022-09-15 11:06 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for DGFX pin_map with rpm 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=20220915103311.5634-1-anshuman.gupta@intel.com \
--to=anshuman.gupta@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=rodrigo.vivi@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