All of lore.kernel.org
 help / color / mirror / Atom feed
From: "André Almeida" <andrealmeid@collabora.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Daniel Vetter <daniel@ffwll.ch>,
	Kenneth Graunke <kenneth@whitecape.org>
Cc: intel-gfx@lists.freedesktop.org, kernel@collabora.com,
	dri-devel@lists.freedesktop.org
Subject: Enabling sample_c optimization for Broadwell GPUs
Date: Tue, 4 May 2021 20:07:14 -0300	[thread overview]
Message-ID: <e99599bf-f503-3227-8361-afcd3d2a098f@collabora.com> (raw)

Hi there,

While browsing an old downstream kernel, I found a patch[0] that enables 
sample_c optimizations at Broadwell GPUs. The message from the upstream 
commit that enables it for Haswell[1] (and presumably where the code 
at[0] was copied from) states that "[..] later platforms remove this 
bit, and apparently always enable the optimization".

Could you confirm that Broadwell and following architectures enable this 
optimization by default (and thus, patch[0] is a no-op), or should I 
upstream it?

Thanks,
	André

[0] 
https://github.com/ValveSoftware/steamos_kernel/commit/198990f13e1d9429864c177d9441a6559771c5e2

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=944115934436b1ff6cf773a9e9123858ea9ef3da
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2021-05-05  6:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 23:07 André Almeida [this message]
2021-05-05 10:16 ` Enabling sample_c optimization for Broadwell GPUs Rodrigo Vivi
2021-05-05 10:16   ` [Intel-gfx] " Rodrigo Vivi
2021-05-05 15:02   ` André Almeida
2021-05-05 15:02     ` [Intel-gfx] " André Almeida
2021-05-05 15:35 ` Kenneth Graunke
2021-05-05 15:35   ` [Intel-gfx] " Kenneth Graunke

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=e99599bf-f503-3227-8361-afcd3d2a098f@collabora.com \
    --to=andrealmeid@collabora.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=kenneth@whitecape.org \
    --cc=kernel@collabora.com \
    --cc=rodrigo.vivi@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.