[Mesa-dev] [PATCH 2/4] gallium: add initial support for conservative rasterization

Marek Olšák maraeo at gmail.com
Sat Mar 24 00:33:52 UTC 2018


On Wed, Mar 21, 2018 at 8:04 PM, Roland Scheidegger <sroland at vmware.com>
wrote:

> Am 22.03.2018 um 00:43 schrieb Ilia Mirkin:
> > On Wed, Mar 21, 2018 at 7:37 PM, Roland Scheidegger <sroland at vmware.com>
> wrote:
> >> Personally I'm not a big proponent on propagating single-vendor
> >> extensions (which are useless for anything but one specific driver) more
> >> or less directly through to gallium.
> >> There's an intel extension doing similar things already too.
> >> Ideally we'd end up with some bits in gallium which can do whatever the
> >> standardized version of it is going to require in some sensible way - at
> >> least I'd hope that such an extension will surface...
> >
> > Agreed. When/if such an extension materializes, we can adjust the
> > gallium API in a logical way to cover all the cases. Until then, this
> > is the functionality that exists on the GPUs in question.
> >
>
> I'm wondering, which bits of these could be done on AMD gpus too? Vega
> chips support conservative rasterization too.
> My guess is that what will end up in a standardized extension is
> probably similar to what's supported by d3d...
>
> I'm not just not sure it's really worth the trouble of bothering the
> gallium interface with basically experimental additions. From what I can
> tell you could instead implement intel's extension and expose that on
> nvidia gpus instead (albeit I'm not sure nvidia can do all of that
> neither) - from a quick look the interfaces would be quite different if
> you started with that instead.
>
> But whatever, I'm not too concerned, but maybe the AMD guys are...
>

I'm totally OK with this interface even though I don't have information
right now about how to implement the feature on AMD.

If people want to support their driver and want to add interfaces that no
other driver cares about, that's also fine. I guess the motivation is to
compete with the closed source driver, which is very reasonable. If/when we
implement the feature, we might make necessary adjustments to the interface
to support AMD while making sure that the adjustments don't affect other
drivers.

Marek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180323/cad22e2a/attachment.html>


More information about the mesa-dev mailing list