qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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: [Qemu-devel] Re: Another SIGFPE in display code, now in cirrus
Date: Wed, 12 May 2010 19:57:39 +0300	[thread overview]
Message-ID: <4BEADE03.7040405@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1005121750480.11380@kaball-desktop>

On 05/12/2010 07:55 PM, Stefano Stabellini wrote:
>
>>> 3CEh index 26h W(R/W):  BLT Source Pitch                              (5426 +)
>>> bit 0-11  (5426-28) Number of bytes in a scanline at the source.
>>>       0-12  (5429 +)  do
>>>
>>> if the source BLT is supposed to be the number of bytes in a scanline at
>>> the source, then 0 is not a correct value for it.
>>>
>>>        
>> 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.
>
> Without any clear indication of what a Cirrus Logic graphic card would
> have done here, I would choose the safest answer that is disregard the
> "delicate" case (if it doesn't break Windows NT).
>    

My guess is that the src or dst address simply doesn't increment.  I 
think it's also fine to ignore the operation completely.

> However I don't mind if we try to handle this case too, provided
> that we handle it well, without SIGFPEs that is :)
>    


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

  reply	other threads:[~2010-05-12 16:57 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 [this message]
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
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=4BEADE03.7040405@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).