From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53494) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X1tqL-0007if-AR for qemu-devel@nongnu.org; Tue, 01 Jul 2014 04:55:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X1tqD-0000IO-OU for qemu-devel@nongnu.org; Tue, 01 Jul 2014 04:55:13 -0400 Received: from cantor2.suse.de ([195.135.220.15]:38256 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X1tqD-0000HI-IL for qemu-devel@nongnu.org; Tue, 01 Jul 2014 04:55:05 -0400 Message-ID: <53B270CD.7080907@suse.de> Date: Tue, 01 Jul 2014 10:26:53 +0200 From: Alexander Graf MIME-Version: 1.0 References: <1402974463.7661.102.camel@pasglop> <1403001900.1614.10.camel@nilsson.home.kraxel.org> <1403003721.7661.148.camel@pasglop> <1403006267.1614.14.camel@nilsson.home.kraxel.org> <1403040734.7661.173.camel@pasglop> <1403090315.13406.3.camel@nilsson.home.kraxel.org> <1403096614.7661.208.camel@pasglop> <1403170570.22530.5.camel@nilsson.home.kraxel.org> <1403329021.4587.78.camel@pasglop> <1403403026.4587.108.camel@pasglop> <1404126876.24066.23.camel@nilsson.home.kraxel.org> <1404131521.29546.3.camel@pasglop> <1404202838.24066.52.camel@nilsson.home.kraxel.org> In-Reply-To: <1404202838.24066.52.camel@nilsson.home.kraxel.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC] qemu VGA endian swap low level drawing changes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann , Benjamin Herrenschmidt Cc: Alexey Kardashevskiy , Paolo Bonzini , "qemu-devel@nongnu.org" On 01.07.14 10:20, Gerd Hoffmann wrote: > On Mo, 2014-06-30 at 22:32 +1000, Benjamin Herrenschmidt wrote: >> On Mon, 2014-06-30 at 13:14 +0200, Gerd Hoffmann wrote: >>> Hi, >>> >>>> From what I can tell, we only ever call the cursor drawing callback on >>>> non-shared surfaces. Should I deduce that the HW cursor emulation simply >>>> doesn't work when using shared surfaces ? Or is there another path I >>>> have missed to handle it ? >>> Hmm. Looks like hw-cursor-on-shared-surface broken indeed. Need to dig >>> out a guest which actually uses it & go figure when testing your patch >>> series ... >> I don't think I broke it much more than it already was but then I >> couldn't find a guest using it. I've tried the plain cirrus DDX in X and >> it didn't have any problem... maybe windows ? > Nope. windows xp doesn't use it. Anything newer doesn't ship with > cirrus drivers any more (and uses vesa bios support). > > Looking at the code the cirrus hardware cursor supports two colors only > (and some funky xor mode). Guess it simply doesn't cut it as you can't > have your cursors drop shadows with that, so guests are ignoring it. Windows NT 4 might use it. I remember that I had issues running NT4 with Cirrus emulation a while back. > >> Right. A quick fix would be to add a flag to force always using a shadow >> surface and set it in cirrus ... I'm not sure anybody will notice the >> performance difference. > I suspect we can rip out hw cursor emulation and nobody will notice the > difference either ... Very likely ;). Though I think we're better off keeping it around to make sure we're still compatible with ancient guests (Windows 3.1 might use it too). Making it slow however shouldn't make any difference at all. Alex