From: Gerd Hoffmann <kraxel@redhat.com>
To: Wolfgang Bumiller <w.bumiller@proxmox.com>
Cc: "Alberto Garcia" <berto@igalia.com>,
"Huawei PSIRT" <psirt@huawei.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Qemu Developers" <qemu-devel@nongnu.org>,
"P J P" <ppandit@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] display: cirrus: check vga bits per pixel(bpp) value
Date: Mon, 23 Jan 2017 12:56:58 +0100 [thread overview]
Message-ID: <1485172618.2149.14.camel@redhat.com> (raw)
In-Reply-To: <20170120094635.GA28338@olga.wb>
Hi,
> > > What seems to happen is that blit_is_unsafe() is also called for
> > > CIRRUS_BLTMODE_PATTERNCOPY, but in this case cirrus_blt_srcpitch is
> > > not used. However, because of this new check if its value is 0 then
> > > cirrus_bitblt_common_patterncopy() returns early and becomes a no-op.
> >
> > inflight vga queue pull request has a fix for that.
>
> Do you mean:
> [PATCH] display: cirrus: ignore source pitch value as needed in blit_is_unsafe
> (Message-Id: <20170109203520.5619-1-brogers@suse.com>)
Yes.
> Because I'm still seeing artifacts on some setups (eg. on win XP).
> As far as I can tell the check is still too strong:
> The rops used by cirrus_bitblt_common_patterncopy seem to only be using
> the destination pitch as far as I can see (all functions in
> cirrus_vga_rop2.h) and in my tests only the destination pitch got
> filled in, the source pitch was left as zero. Adapting the check when
> coming from cirrus_bitblt_common_patterncopy seems to fix the issue for
> me.
> From a3be50cc3e3bb0f5eb784d30048b88333366bdca Mon Sep 17 00:00:00 2001
> From: Wolfgang Bumiller <w.bumiller@proxmox.com>
> Date: Fri, 20 Jan 2017 09:44:39 +0100
> Subject: [PATCH] cirrus: allow zero source pitch in pattern fill rops
>
> The rops used by cirrus_bitblt_common_patterncopy only use
> the destination pitch, so the source pitch shoul allowed to
> be zero.
>
> Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
Looks good to me, can you 'git send-email' it to the list?
thanks,
Gerd
prev parent reply other threads:[~2017-01-23 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 7:45 [Qemu-devel] [PATCH] display: cirrus: check vga bits per pixel(bpp) value P J P
2016-11-15 16:43 ` P J P
2016-11-16 14:13 ` Marc-André Lureau
2016-11-28 6:22 ` P J P
2016-12-05 7:33 ` P J P
2017-01-11 14:59 ` Alberto Garcia
2017-01-11 20:43 ` Gerd Hoffmann
2017-01-20 9:46 ` Wolfgang Bumiller
2017-01-23 11:56 ` Gerd Hoffmann [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=1485172618.2149.14.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=berto@igalia.com \
--cc=marcandre.lureau@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=ppandit@redhat.com \
--cc=psirt@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=w.bumiller@proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).