From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org,
Benjamin Gaignard <benjamin.gaignard@st.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/rect: Keep the clipped dst rectangle in place
Date: Fri, 22 Nov 2019 19:25:39 +0200 [thread overview]
Message-ID: <20191122172539.GP1208@intel.com> (raw)
In-Reply-To: <20191120171138.GI1208@intel.com>
On Wed, Nov 20, 2019 at 07:11:38PM +0200, Ville Syrjälä wrote:
> On Wed, Nov 20, 2019 at 05:43:40PM +0100, Daniel Vetter wrote:
> > On Wed, Nov 20, 2019 at 06:25:12PM +0200, Ville Syrjala wrote:
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > >
> > > Now that we've constrained the clipped source rectangle such
> > > that it can't have negative dimensions doing the same for the
> > > dst rectangle seems appropriate. Should at least result in
> > > the clipped src and dst rectangles being a bit more consistent
> > > with each other.
> > >
> > > Cc: Benjamin Gaignard <benjamin.gaignard@st.com>
> > > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > selftests for this stuff? Looks like the prime example, write testcase
> > proving code is busted, fix it, everyone celebrate?
>
> Yeah, seems like a good idea. Though I'll have to figure out if it's
> actually broken or not ;)
I *think* the only problem is that the clip can result in a visible
source rectangle when this happens. The dst rectangle will still
be correctly invisible so hopefully not a big deal. But I guess we
might as well fix it, and I can do a selftest which makes sure
both src and dst come out invisible.
>
> Hmm. Ouch. There's seems to be a div by zero lurking in there if
> dst_w/h == 0. I wonder why nothing has hit that.
Definitely real. I'll fix it and toss in a selftest.
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org,
Benjamin Gaignard <benjamin.gaignard@st.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/rect: Keep the clipped dst rectangle in place
Date: Fri, 22 Nov 2019 19:25:39 +0200 [thread overview]
Message-ID: <20191122172539.GP1208@intel.com> (raw)
Message-ID: <20191122172539.LN6Nq4iRTk_FCrA2rZ3vGDE8nKbDYbrMeoQPaq-DOkI@z> (raw)
In-Reply-To: <20191120171138.GI1208@intel.com>
On Wed, Nov 20, 2019 at 07:11:38PM +0200, Ville Syrjälä wrote:
> On Wed, Nov 20, 2019 at 05:43:40PM +0100, Daniel Vetter wrote:
> > On Wed, Nov 20, 2019 at 06:25:12PM +0200, Ville Syrjala wrote:
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > >
> > > Now that we've constrained the clipped source rectangle such
> > > that it can't have negative dimensions doing the same for the
> > > dst rectangle seems appropriate. Should at least result in
> > > the clipped src and dst rectangles being a bit more consistent
> > > with each other.
> > >
> > > Cc: Benjamin Gaignard <benjamin.gaignard@st.com>
> > > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > selftests for this stuff? Looks like the prime example, write testcase
> > proving code is busted, fix it, everyone celebrate?
>
> Yeah, seems like a good idea. Though I'll have to figure out if it's
> actually broken or not ;)
I *think* the only problem is that the clip can result in a visible
source rectangle when this happens. The dst rectangle will still
be correctly invisible so hopefully not a big deal. But I guess we
might as well fix it, and I can do a selftest which makes sure
both src and dst come out invisible.
>
> Hmm. Ouch. There's seems to be a div by zero lurking in there if
> dst_w/h == 0. I wonder why nothing has hit that.
Definitely real. I'll fix it and toss in a selftest.
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-22 17:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 16:25 [PATCH 1/2] drm/rect: Keep the scaled clip bounded Ville Syrjala
2019-11-20 16:25 ` [Intel-gfx] " Ville Syrjala
2019-11-20 16:25 ` [PATCH 2/2] drm/rect: Keep the clipped dst rectangle in place Ville Syrjala
2019-11-20 16:25 ` [Intel-gfx] " Ville Syrjala
2019-11-20 16:43 ` Daniel Vetter
2019-11-20 16:43 ` [Intel-gfx] " Daniel Vetter
2019-11-20 17:11 ` Ville Syrjälä
2019-11-20 17:11 ` Ville Syrjälä
2019-11-20 19:55 ` Benjamin GAIGNARD
2019-11-20 19:55 ` [Intel-gfx] " Benjamin GAIGNARD
2019-11-22 17:25 ` Ville Syrjälä [this message]
2019-11-22 17:25 ` Ville Syrjälä
2019-11-20 22:01 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/rect: Keep the scaled clip bounded Patchwork
2019-11-20 22:01 ` [Intel-gfx] " Patchwork
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=20191122172539.GP1208@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=benjamin.gaignard@st.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox