From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Paulo Zanoni <paulo.r.zanoni@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: make i915_stolen_to_physical() return phys_addr_t
Date: Fri, 27 Jan 2017 15:59:19 +0200 [thread overview]
Message-ID: <20170127135919.GV31595@intel.com> (raw)
In-Reply-To: <1485461947-16030-1-git-send-email-paulo.r.zanoni@intel.com>
On Thu, Jan 26, 2017 at 06:19:07PM -0200, Paulo Zanoni wrote:
> The i915_stolen_to_physical() function has 'unsigned long' as its
> return type but it returns the 'base' variable, which is of type
> 'u32'. The only place where this function is called assigns the
> returned value to dev_priv->mm.stolen_base, which is of type
> 'phys_addr_t'. The return value is actually a physical address and
> everything else in the stolen memory code seems to be using
> phys_addr_t, so fix i915_stolen_to_physical() to use phys_addr_t.
Size of phys_addr_t depends on PAE no? So what if someone were to boot
a !PAE kernel on a machine where stolen lives somewhere >4GiB?
>
> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> ---
> drivers/gpu/drm/i915/i915_gem_stolen.c | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c b/drivers/gpu/drm/i915/i915_gem_stolen.c
> index 127d698..0816ebd 100644
> --- a/drivers/gpu/drm/i915/i915_gem_stolen.c
> +++ b/drivers/gpu/drm/i915/i915_gem_stolen.c
> @@ -79,12 +79,12 @@ void i915_gem_stolen_remove_node(struct drm_i915_private *dev_priv,
> mutex_unlock(&dev_priv->mm.stolen_lock);
> }
>
> -static unsigned long i915_stolen_to_physical(struct drm_i915_private *dev_priv)
> +static phys_addr_t i915_stolen_to_physical(struct drm_i915_private *dev_priv)
> {
> struct pci_dev *pdev = dev_priv->drm.pdev;
> struct i915_ggtt *ggtt = &dev_priv->ggtt;
> struct resource *r;
> - u32 base;
> + phys_addr_t base;
>
> /* Almost universally we can find the Graphics Base of Stolen Memory
> * at register BSM (0x5c) in the igfx configuration space. On a few
> @@ -196,7 +196,7 @@ static unsigned long i915_stolen_to_physical(struct drm_i915_private *dev_priv)
> if (INTEL_GEN(dev_priv) <= 4 &&
> !IS_G33(dev_priv) && !IS_PINEVIEW(dev_priv) && !IS_G4X(dev_priv)) {
> struct {
> - u32 start, end;
> + phys_addr_t start, end;
> } stolen[2] = {
> { .start = base, .end = base + ggtt->stolen_size, },
> { .start = base, .end = base + ggtt->stolen_size, },
> @@ -228,11 +228,12 @@ static unsigned long i915_stolen_to_physical(struct drm_i915_private *dev_priv)
>
> if (stolen[0].start != stolen[1].start ||
> stolen[0].end != stolen[1].end) {
> + phys_addr_t end = base + ggtt->stolen_size - 1;
> DRM_DEBUG_KMS("GTT within stolen memory at 0x%llx-0x%llx\n",
> (unsigned long long)ggtt_start,
> (unsigned long long)ggtt_end - 1);
> - DRM_DEBUG_KMS("Stolen memory adjusted to 0x%x-0x%x\n",
> - base, base + (u32)ggtt->stolen_size - 1);
> + DRM_DEBUG_KMS("Stolen memory adjusted to %pa - %pa\n",
> + &base, &end);
> }
> }
>
> @@ -261,8 +262,9 @@ static unsigned long i915_stolen_to_physical(struct drm_i915_private *dev_priv)
> * range. Apparently this works.
> */
> if (r == NULL && !IS_GEN3(dev_priv)) {
> - DRM_ERROR("conflict detected with stolen region: [0x%08x - 0x%08x]\n",
> - base, base + (uint32_t)ggtt->stolen_size);
> + phys_addr_t end = base + ggtt->stolen_size;
> + DRM_ERROR("conflict detected with stolen region: [%pa - %pa]\n",
> + &base, &end);
> base = 0;
> }
> }
> --
> 2.7.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-01-27 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 20:19 [PATCH] drm/i915: make i915_stolen_to_physical() return phys_addr_t Paulo Zanoni
2017-01-26 21:21 ` Chris Wilson
2017-01-27 0:54 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-01-27 13:59 ` Ville Syrjälä [this message]
2017-01-27 14:20 ` [PATCH] " Chris Wilson
2017-01-27 14:38 ` Ville Syrjälä
2017-01-27 14:42 ` Chris Wilson
2017-01-27 15:06 ` Ville Syrjälä
2017-01-27 15:16 ` Chris Wilson
2017-01-27 15:44 ` Paulo Zanoni
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=20170127135919.GV31595@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@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).