From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Thomas Richter <thor@math.tu-berlin.de>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/2] drm/i915: 830M regression fixes
Date: Tue, 7 Jan 2014 21:09:10 +0200 [thread overview]
Message-ID: <20140107190910.GE4800@intel.com> (raw)
In-Reply-To: <20140107165910.GG8991@nuc-i3427.alporthouse.com>
On Tue, Jan 07, 2014 at 04:59:10PM +0000, Chris Wilson wrote:
> On Tue, Jan 07, 2014 at 04:12:06PM +0100, Thomas Richter wrote:
> > On 01/07/2014 03:15 PM, ville.syrjala@linux.intel.com wrote:
> > >From: Ville Syrjälä<ville.syrjala@linux.intel.com>
> > >
> > >Looks like I managed to break 830M in a few different ways recently. But I
> > >recently found one for myself so hopefully that'll not happen again.
> > >
> > >I have a few other things lined up for 830M, but these are the quick fixes
> > >that should get us back to the state we had before.
> >
> > Thanks, Ville!
> >
> > As a related note, I found that with the latest kernel, "uxa"
> > drawing of filled rectangles became very slow (and sna is still too
> > broken to be useful, sorry). Would you know which file I should look
> > into to check for something like this? The client application only
> > submits plain X11 calls, the render acceleration or composition
> > should (?) not play a role here. It's really a plain simple filled
> > rectangle (or many of them) that became notably slow.
>
> Wtf? What's up with SNA? There's a solitary report that cache coherency
> on 830GM requires some workaround, on which I'd hoped that Daniel could
> run igt to confirm (and now perhaps Ville might fancy the challenge).
> Other than that, judging by my 845g, it should be solid.
FWIW I haven't seen any issues w/ SNA on either 830 or 855, but I must
admit that I've not done any extensive testing on either.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-01-07 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <23446_1389104159_52CC0C1F_23446_3565_1_1389104137-6627-1-git-send-email-ville.syrjala@linux.intel.com>
2014-01-07 15:12 ` [PATCH 0/2] drm/i915: 830M regression fixes Thomas Richter
2014-01-07 16:59 ` Chris Wilson
2014-01-07 19:09 ` Ville Syrjälä [this message]
2014-01-07 14:15 ville.syrjala
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=20140107190910.GE4800@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thor@math.tu-berlin.de \
/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