From: "samuel.pitoiset" <samuel.pitoiset-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
Cc: "mesa-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<mesa-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
"10.4 10.5"
<mesa-stable-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
"nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [Mesa-dev] [PATCH] nvc0: fix geometry program revalidation of clipping params
Date: Thu, 16 Jul 2015 23:49:01 +0200 [thread overview]
Message-ID: <55A826CD.2010305@gmail.com> (raw)
In-Reply-To: <CAKb7UvgrshmzTjCvd4fJLJyP1BEiU0+3LRqCiUJd==BWy+kE2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Seems reasonable.
Please, let me know the result of the full piglit run.
If everything is okay, this patch is :
Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>
On 13/07/2015 20:08, Ilia Mirkin wrote:
> This was, btw, introduced in commit 3a8ae6ac243b (nvc0: adapt to new
> clip state). Back then there was no real geometry support yet.
>
> On Mon, Jul 13, 2015 at 2:05 PM, Ilia Mirkin <imirkin@alum.mit.edu> wrote:
>> Any one which, after using a geometry shader, enables an extra clip
>> distance. i.e. none.
>>
>> On Mon, Jul 13, 2015 at 4:16 AM, Samuel Pitoiset
>> <samuel.pitoiset@gmail.com> wrote:
>>> What piglit test does this fix?
>>>
>>> On Sat, Jul 11, 2015 at 7:13 PM, Ilia Mirkin <imirkin@alum.mit.edu> wrote:
>>>> Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
>>>> Cc: mesa-stable@lists.freedesktop.org
>>>> ---
>>>>
>>>> Even though in practice a geometry program will never be using UCP's,
>>>> we still were revalidating (aka recompiling) the program when more
>>>> clip planes became enabled (which also are used for regular clip
>>>> distances).
>>>>
>>>> This seems like it should have led to massive fail, but I guess you
>>>> don't change the number of clip planes when using geometry shaders.
>>>> But I'm going to put this through a full piglit run just in case
>>>> there's something I'm missing.
>>>>
>>>> src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c
>>>> b/src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c
>>>> index 785e52e..11f2b10 100644
>>>> --- a/src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c
>>>> +++ b/src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c
>>>> @@ -339,7 +339,7 @@ nvc0_check_program_ucps(struct nvc0_context *nvc0,
>>>> nvc0_vertprog_validate(nvc0);
>>>> else
>>>> if (likely(vp == nvc0->gmtyprog))
>>>> - nvc0_vertprog_validate(nvc0);
>>>> + nvc0_gmtyprog_validate(nvc0);
>>>> else
>>>> nvc0_tevlprog_validate(nvc0);
>>>> }
>>>> --
>>>> 2.3.6
>>>>
>>>> _______________________________________________
>>>> mesa-dev mailing list
>>>> mesa-dev@lists.freedesktop.org
>>>> http://lists.freedesktop.org/mailman/listinfo/mesa-dev
>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Samuel Pitoiset.
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
prev parent reply other threads:[~2015-07-16 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 17:13 [PATCH] nvc0: fix geometry program revalidation of clipping params Ilia Mirkin
2015-07-13 8:16 ` Samuel Pitoiset
[not found] ` <CAJd1Ru5fmsDDftu0pkQtfqtzUaoWV8TCRHm=TiXgtmb-jD-wvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-13 18:05 ` [Mesa-dev] " Ilia Mirkin
[not found] ` <CAKb7Uvj1KLHokGvznQ=722-D3PFx691S4kUBODJG-dSyDvkNyA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-13 18:08 ` Ilia Mirkin
[not found] ` <CAKb7UvgrshmzTjCvd4fJLJyP1BEiU0+3LRqCiUJd==BWy+kE2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-16 21:49 ` samuel.pitoiset [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=55A826CD.2010305@gmail.com \
--to=samuel.pitoiset-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org \
--cc=mesa-dev-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=mesa-stable-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.