From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org, Taketo Kabe <fdporg@vega.pgw.jp>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Account for TSEG size when determining 865G stolen base
Date: Thu, 11 Aug 2016 19:38:24 +0300 [thread overview]
Message-ID: <20160811163824.GR4329@intel.com> (raw)
In-Reply-To: <20160809085347.GA21147@nuc-i3427.alporthouse.com>
On Tue, Aug 09, 2016 at 09:53:47AM +0100, Chris Wilson wrote:
> On Mon, Aug 08, 2016 at 01:58:39PM +0300, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Looks like the TSEG lives just above TOUD, stolen comes after TSEG.
> >
> > The spec seems somewhat self-contradictory in places, in the ESMRAMC
> > register desctription it says:
> > TSEG Size:
> > 10=(TOUD + 512 KB) to TOUD
> > 11 =(TOUD + 1 MB) to TOUD
> >
> > so that agrees with TSEG being at TOUD. But the example given
> > elsehwere in the spec says:
> >
> > TOUD equals 62.5 MB = 03E7FFFFh
> > TSEG selected as 512 KB in size,
> > Graphics local memory selected as 1 MB in size
> > General System RAM available in system = 62.5 MB
> > General system RAM range00000000h to 03E7FFFFh
> > TSEG address range03F80000h to 03FFFFFFh
> > TSEG pre-allocated from03F80000h to 03FFFFFFh
> > Graphics local memory pre-allocated from03E80000h to 03F7FFFFh
>
> Found that example:
>
> """
> Notes on Pre-Allocated Memory for Graphics
>
> These register bits control the use of memory from main memory space as
> graphics local memory. The memory for TSEG is pre-allocated first and
> then the graphics local memory is pre-allocated.
> """
>
> > so here we have TSEG above stolen.
> >
> > Real world evidence agrees with the TOUD->TSEG->stolen order however, so
> > let's fix up the code to account for the TSEG size.
> >
> > Cc: Taketo Kabe <fdporg@vega.pgw.jp>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Cc: Thomas Gleixner <tglx@linutronix.de>
> > Cc: Ingo Molnar <mingo@redhat.com>
> > Cc: "H. Peter Anvin" <hpa@zytor.com>
> > Cc: x86@kernel.org
> > Cc: stable@vger.kernel.org
> > Fixes: 0ad98c74e093 ("drm/i915: Determine the stolen memory base address on gen2")
> > Fixes: a4dff76924fe ("x86/gpu: Add Intel graphics stolen memory quirk for gen2 platforms")
> > Reported-by: Taketo Kabe <fdporg@vega.pgw.jp>
> > Tested-by: Taketo Kabe <fdporg@vega.pgw.jp>
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96473
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Link: http://download.intel.com/design/chipsets/datashts/25251405.pdf
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Didn't see any objections from x86 folks, so I went and pushed this to
dinq. Thanks for the review.
--
Ville Syrjälä
Intel OTC
prev parent reply other threads:[~2016-08-11 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 10:58 [PATCH] drm/i915: Account for TSEG size when determining 865G stolen base ville.syrjala
2016-08-08 11:25 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-08-09 5:44 ` Ville Syrjälä
2016-08-09 8:53 ` [PATCH] " Chris Wilson
2016-08-11 16:38 ` Ville Syrjälä [this message]
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=20160811163824.GR4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=fdporg@vega.pgw.jp \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox