From: Avi Kivity <avi@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Brian Kress <kressb@moose.net>, Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel <qemu-devel@nongnu.org>,
KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Re: Another SIGFPE in display code, now in cirrus
Date: Thu, 13 May 2010 09:49:17 +0300 [thread overview]
Message-ID: <4BEBA0ED.9010009@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1005121855230.11380@kaball-desktop>
On 05/12/2010 09:11 PM, Stefano Stabellini wrote:
> On Wed, 12 May 2010, Jamie Lokier wrote:
>
>> Stefano Stabellini wrote:
>>
>>> On Wed, 12 May 2010, Avi Kivity wrote:
>>>
>>>> It's useful if you have a one-line horizontal pattern you want to
>>>> propagate all over.
>>>>
>>>
>>> It might be useful all right, but it is not entirely clear what the
>>> hardware should do in this situation from the documentation we have, and
>>> certainly the current state of the cirrus emulation code doesn't help.
>>>
>> It's quite a reasonable thing for hardware to do, even if not documented.
>> It would be surprising if the hardware didn't copy the one-line pattern.
>>
>
> All right then, you convinced me :)
>
> This is my proposed solution, however it is untested with Windows NT.
>
>
> Signed-off-by: Stefano Stabellini<stefano.stabellini@eu.citrix.com>
>
> ---
>
>
>
> diff --git a/hw/cirrus_vga.c b/hw/cirrus_vga.c
> index 9f61a01..a7f0d3c 100644
> --- a/hw/cirrus_vga.c
> +++ b/hw/cirrus_vga.c
> @@ -676,15 +676,17 @@ static void cirrus_do_copy(CirrusVGAState *s, int dst, int src, int w, int h)
> int sx, sy;
> int dx, dy;
> int width, height;
> + uint32_t start_addr, line_offset, line_compare;
> int depth;
> int notify = 0;
>
> depth = s->vga.get_bpp(&s->vga) / 8;
> s->vga.get_resolution(&s->vga,&width,&height);
> + s->vga.get_offsets(&s->vga,&line_offset,&start_addr,&line_compare);
>
> /* extra x, y */
> - sx = (src % ABS(s->cirrus_blt_srcpitch)) / depth;
> - sy = (src / ABS(s->cirrus_blt_srcpitch));
> + sx = (src % line_offset) / depth;
> + sy = (src / line_offset);
>
Does anything prevent the guest from programming the CRTC display pitch
to 0?
> dx = (dst % ABS(s->cirrus_blt_dstpitch)) / depth;
> dy = (dst / ABS(s->cirrus_blt_dstpitch));
>
> @@ -725,18 +727,23 @@ static void cirrus_do_copy(CirrusVGAState *s, int dst, int src, int w, int h)
> s->cirrus_blt_dstpitch, s->cirrus_blt_srcpitch,
> s->cirrus_blt_width, s->cirrus_blt_height);
>
> - if (notify)
> - qemu_console_copy(s->vga.ds,
> - sx, sy, dx, dy,
> - s->cirrus_blt_width / depth,
> - s->cirrus_blt_height);
> -
> - /* we don't have to notify the display that this portion has
> - changed since qemu_console_copy implies this */
> -
> - cirrus_invalidate_region(s, s->cirrus_blt_dstaddr,
> - s->cirrus_blt_dstpitch, s->cirrus_blt_width,
> - s->cirrus_blt_height);
> + if (ABS(s->cirrus_blt_dstpitch) != line_offset ||
> + ABS(s->cirrus_blt_srcpitch) != line_offset) {
> + /* this is not going to happen very often */
> + vga_hw_invalidate();
>
I think we need to consider only dstpitch for a full invalidate. We
might be copying an offscreen bitmap into the screen, and srcpitch is
likely to be the bitmap width instead of the screen pitch.
> + } else {
> + if (notify)
> + /* we don't have to notify the display that this portion has
> + changed since qemu_console_copy implies this */
> + qemu_console_copy(s->vga.ds,
> + sx, sy, dx, dy,
> + s->cirrus_blt_width / depth,
> + s->cirrus_blt_height);
> + else
> + cirrus_invalidate_region(s, s->cirrus_blt_dstaddr,
> + s->cirrus_blt_dstpitch, s->cirrus_blt_width,
> + s->cirrus_blt_height);
> + }
> }
>
> static int cirrus_bitblt_videotovideo_copy(CirrusVGAState * s)
> diff --git a/hw/cirrus_vga_rop.h b/hw/cirrus_vga_rop.h
> index 39a7b72..80f135b 100644
> --- a/hw/cirrus_vga_rop.h
> +++ b/hw/cirrus_vga_rop.h
> @@ -32,10 +32,10 @@ glue(cirrus_bitblt_rop_fwd_, ROP_NAME)(CirrusVGAState *s,
> dstpitch -= bltwidth;
> srcpitch -= bltwidth;
>
> - if (dstpitch< 0 || srcpitch< 0) {
> - /* is 0 valid? srcpitch == 0 could be useful */
> + if (dstpitch< 0)
> return;
> - }
> + if (srcpitch< 0)
> + srcpitch = 0;
>
Why?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2010-05-13 11:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BE32178.2090103@msgid.tls.msk.ru>
2010-05-10 7:41 ` [Qemu-devel] Re: Another SIGFPE in display code, now in cirrus Avi Kivity
2010-05-10 8:15 ` Avi Kivity
2010-05-12 12:20 ` Stefano Stabellini
2010-05-12 12:36 ` Avi Kivity
2010-05-12 13:45 ` Stefano Stabellini
2010-05-12 14:27 ` Avi Kivity
2010-05-12 15:57 ` Stefano Stabellini
2010-05-12 16:07 ` Avi Kivity
2010-05-12 16:55 ` Stefano Stabellini
2010-05-12 16:57 ` Avi Kivity
2010-05-12 17:07 ` Jamie Lokier
2010-05-12 18:11 ` Stefano Stabellini
2010-05-12 19:12 ` Michael Tokarev
2010-05-13 6:49 ` Avi Kivity [this message]
2010-05-13 13:48 ` Stefano Stabellini
2010-05-13 14:13 ` Michael Tokarev
2010-05-13 18:03 ` Stefano Stabellini
2010-05-13 16:04 ` Jamie Lokier
2010-05-28 20:51 ` Michael Tokarev
2010-05-30 8:24 ` Avi Kivity
2010-05-13 7:36 ` Paolo Bonzini
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=4BEBA0ED.9010009@redhat.com \
--to=avi@redhat.com \
--cc=kressb@moose.net \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.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).