public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Anshuman Gupta <anshuman.gupta@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: daniel@ffwll.ch, chris.p.wilson@intel.com, rodrigo.vivi@intel.com
Subject: [Intel-gfx] [RFC 0/1] Avoid parent bridge rpm on mmap mappings
Date: Mon,  8 Aug 2022 16:05:54 +0530	[thread overview]
Message-ID: <20220808103555.345-1-anshuman.gupta@intel.com> (raw)

RFC proposal to get community feedback to handle the lmem
mmap memory mappings. We can have two solutions.

1. Avoid rpm for any mmap mapping.
2. Update the page tables while entering to runtime suspend to raise
   a page fault while device in D3.

Solution 2 will incur huge latency versus solution 1 which effectively 
disable the runtime PM.

Caveat with solution 1 that, it doesn't address the case when user 
directly maps PCI Bar resource i.e. below mentioned resource. 
"/sys/bus/pci/devices/0000\:03\:00.0/resource2" 

Anshuman Gupta (1):
  drm/i915/dgfx: Avoid parent bridge rpm on mmap mappings

 drivers/gpu/drm/i915/gem/i915_gem_mman.c | 11 ++++++++
 drivers/gpu/drm/i915/gem/i915_gem_ttm.c  |  8 ++++++
 drivers/gpu/drm/i915/intel_runtime_pm.c  | 35 ++++++++++++++++++++++++
 drivers/gpu/drm/i915/intel_runtime_pm.h  |  2 ++
 4 files changed, 56 insertions(+)

-- 
2.26.2


             reply	other threads:[~2022-08-08 10:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 10:35 Anshuman Gupta [this message]
2022-08-08 10:35 ` [Intel-gfx] [RFC 1/1] drm/i915/dgfx: Avoid parent bridge rpm on mmap mappings Anshuman Gupta
2022-08-09 15:05   ` Rodrigo Vivi
2022-08-10  4:36     ` Gupta, Anshuman
2022-08-17  5:41     ` Gupta, Anshuman
2022-08-08 11:42 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-08-08 12:05 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=20220808103555.345-1-anshuman.gupta@intel.com \
    --to=anshuman.gupta@intel.com \
    --cc=chris.p.wilson@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --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