All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Graunke <kenneth@whitecape.org>
To: "Xiang, Haihao" <haihao.xiang@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	"libva@lists.freedesktop.org" <libva@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Make sample_c messages go faster on Haswell.
Date: Mon, 05 Jan 2015 23:03:31 -0800	[thread overview]
Message-ID: <1877286.PUpbg76clx@vakarian> (raw)
In-Reply-To: <1420526376.2355.77.camel@xhh-u64>


[-- Attachment #1.1: Type: text/plain, Size: 2453 bytes --]

On Tuesday, January 06, 2015 02:39:36 PM Xiang, Haihao wrote:
> On Mon, 2015-01-05 at 21:54 -0800, Kenneth Graunke wrote:
> > On Tuesday, January 06, 2015 01:11:53 PM Xiang, Haihao wrote:
> > > 
> > > Hi Kenneth,
> > > 
> > > How did you test OSD ? I can't reproduce the issue you mentioned, OSD
> > > works well for me when using mplayer-vaapi with the latest
> > > libva/libva-intel-driver master branch.
> > > 
> > > I tried your patch, what surprised me is OSD still works well after
> > > applying your patch. It seems your patch didn't disable the palette.
> > > 
> > > Thanks
> > > Haihao
> > 
> > I ran:
> > 
> > mplayer -osdlevel 3 -vo vaapi big_buck_bunny_720p_stereo.ogg
> > 
> > For me, the OSD text is solid green, with hard edges.
> 
> The OSD text is white for me when using mplayer -osdlevel 3 -vo vaapi
> xxx. If possible, could you update your mplayer ?

Huh.  I'm using the Arch Linux package of mplayer-vaapi 36265-13,
which seems to be the most recent subversion commit ID.  I've never seen
white text on my Haswell system - it seems to be consistently dark green.

> > If you use "-vo gl" or "-vo xv", the OSD is solid white text with a black
> > border around it.  I presume that it's supposed to be white with vaapi as
> > well, but I guess I'm not entirely sure.
> > 
> > It's possible that the optimization doesn't affect the palette as long as
> > you never use sample_c with the paletted textures.
> 
> I verified the palette takes effect in the following way:
> 
> 1. Only support P8A8 format in the driver
> 
> 2. ran the above command and I saw white OSD text
> 
> 3. Only support P4A4 format in the driver and don't use
> 3DSTATE_SAMPLER_PALETTE_LOAD0 to load the value to the texture palette,
> so the palette keeps unchanged. 
> 
> 4. ran the above command and I saw black OSD text.
> 
> 5. Load the right value to the texture palette and ran the above command
> again, I saw white OSD text.
> 
> Hence I think sample_c with the paletted textures is used in the driver.

That sounds like the palette is actually working, then.  Great :)

I doubt that libva would use sample_c - sampling with a shadow comparison?
It looks like it just uses sample and sample+killpix.

I'm pretty sure the sample_c optimization just uses the palette memory as
storage for some stuff, so it's quite possible it just works if you're
only using sample and sample+killpix.

--Ken

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2015-01-06  7:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01  0:23 [PATCH] drm/i915: Make sample_c messages go faster on Haswell Kenneth Graunke
2015-01-05  0:48 ` shuang.he
2015-01-05 13:19 ` Daniel Vetter
2015-01-05 21:39   ` Kenneth Graunke
2015-01-06  5:11     ` Xiang, Haihao
2015-01-06  5:54       ` Kenneth Graunke
2015-01-06  6:39         ` Xiang, Haihao
2015-01-06  7:00           ` [Intel-gfx] " Xiang, Haihao
2015-01-06  7:03           ` Kenneth Graunke [this message]
2015-01-06  7:15             ` Xiang, Haihao
2015-01-06  8:08               ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2014-10-29 22:12 Kenneth Graunke
2014-10-30  8:50 ` Ville Syrjälä
2014-10-30  9:00   ` Ville Syrjälä
2014-10-30  9:32     ` Kenneth Graunke
2014-10-30 11:01       ` Ville Syrjälä
2014-10-30 17:32         ` Kenneth Graunke
2014-10-30 19:26           ` Ville Syrjälä
2014-10-30 19:57             ` Kenneth Graunke
2014-10-31  9:27               ` Ville Syrjälä
2014-10-31  9:43                 ` Jani Nikula
2014-11-03 12:48                 ` Daniel Vetter
2014-11-03 16:15             ` Dave Gordon
2014-11-07 18:46 ` Matt Turner
2014-11-11 10:16   ` Daniel Vetter

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=1877286.PUpbg76clx@vakarian \
    --to=kenneth@whitecape.org \
    --cc=haihao.xiang@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=libva@lists.freedesktop.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 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.