From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: Question about removing memslots Date: Thu, 29 Mar 2012 22:46:02 +1100 Message-ID: <1333021562.3010.11.camel@pasglop> References: <1332919486.2882.88.camel@pasglop> <4F72DBE2.6060909@redhat.com> <1332928770.2882.98.camel@pasglop> <4F72E274.2090007@redhat.com> <1332929849.2882.101.camel@pasglop> <4F72ED38.5000007@redhat.com> <1332968658.2882.108.camel@pasglop> <4F742D3B.2060904@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Alexander Graf , kvm-ppc@vger.kernel.org, Scott Wood , Alex Williamson To: Avi Kivity Return-path: Received: from gate.crashing.org ([63.228.1.57]:54161 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752325Ab2C2LqR (ORCPT ); Thu, 29 Mar 2012 07:46:17 -0400 In-Reply-To: <4F742D3B.2060904@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, 2012-03-29 at 11:36 +0200, Avi Kivity wrote: > > In any case, X seems to avoid it, maybe nobody does color expansion > > nowadays (I suppose modern desktops don't, maybe using ancient X apps > > might trigger that path). So no biggie. I'll have to fix KVM powerpc > > dealing with memslot changes anyways. > > > > Thanks for your help, > > > > As a workaround you can use -vga std or -vga qxl. The latter will work > even better when we have a kernel driver. -vga std works fine, -vga qxl, I haven't tried on ppc yet at all... The thing with cirrus is that it's the default in many cases (libvirt, openstack, you name it it's there...) so it would be good to get it working. I already have fixes for the X driver (mostly some bugs where it stores PCI physical addresses in 32-bit quantities) and I'm fixing cirrusfb now but the later hits the color expansion path, so it looks like we'll have to fix kvm/ppc to do the right thing there too :-) Cheers, Ben.