From: Andi Shyti <andi.shyti@linux.intel.com>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
Matthew Auld <matthew.auld@intel.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915: Exclude reserved stolen from driver use
Date: Wed, 8 Dec 2021 17:18:47 +0200 [thread overview]
Message-ID: <YbDM15H10zZzFxyA@intel.intel> (raw)
In-Reply-To: <20211208145800.27246-2-ramalingam.c@intel.com>
On Wed, Dec 08, 2021 at 08:27:58PM +0530, Ramalingam C wrote:
> From: Chris Wilson <chris@chris-wilson.co.uk>
>
> Remove the portion of stolen memory reserved for private use from driver
> access.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> cc: Matthew Auld <matthew.auld@intel.com>
> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
> ---
> drivers/gpu/drm/i915/gem/i915_gem_stolen.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_stolen.c b/drivers/gpu/drm/i915/gem/i915_gem_stolen.c
> index bce03d74a0b4..6ea3ca21cdf3 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_stolen.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_stolen.c
> @@ -488,6 +488,9 @@ static int i915_gem_init_stolen(struct intel_memory_region *mem)
> return 0;
> }
>
> + /* Exclude the reserved region from driver use */
> + mem->region.end = reserved_base - 1;
> +
> /* It is possible for the reserved area to end before the end of stolen
> * memory, so just consider the start. */
> reserved_total = stolen_top - reserved_base;
> --
> 2.20.1
next prev parent reply other threads:[~2021-12-08 15:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 14:57 [Intel-gfx] [PATCH 0/3] drm/i915: Sanity Check for device memory region Ramalingam C
2021-12-08 14:57 ` Ramalingam C
2021-12-08 14:57 ` [Intel-gfx] [PATCH 1/3] drm/i915: Exclude reserved stolen from driver use Ramalingam C
2021-12-08 14:57 ` Ramalingam C
2021-12-08 15:18 ` Andi Shyti [this message]
2021-12-08 15:20 ` [Intel-gfx] " Andi Shyti
2021-12-08 14:57 ` [Intel-gfx] [PATCH 2/3] drm/i915: Sanitycheck device iomem on probe Ramalingam C
2021-12-08 14:57 ` Ramalingam C
2021-12-08 15:23 ` [Intel-gfx] " Andi Shyti
2021-12-08 15:39 ` Ramalingam C
2021-12-08 14:58 ` [Intel-gfx] [PATCH 3/3] drm/i915: Test all device memory on probing Ramalingam C
2021-12-08 14:58 ` Ramalingam C
2021-12-08 15:26 ` [Intel-gfx] " Andi Shyti
-- strict thread matches above, loose matches on Subject: below --
2021-12-08 15:34 [Intel-gfx] [PATCH 0/3] drm/i915: Sanity Check for device memory region Ramalingam C
2021-12-08 15:34 ` [Intel-gfx] [PATCH 1/3] drm/i915: Exclude reserved stolen from driver use Ramalingam C
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=YbDM15H10zZzFxyA@intel.intel \
--to=andi.shyti@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=ramalingam.c@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 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.