From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, Alexander Graf <agraf@suse.de>,
kvm-ppc@vger.kernel.org, Scott Wood <scottwood@freescale.com>,
Alex Williamson <Alex.Williamson@redhat.com>
Subject: Re: Question about removing memslots
Date: Thu, 29 Mar 2012 22:46:02 +1100 [thread overview]
Message-ID: <1333021562.3010.11.camel@pasglop> (raw)
In-Reply-To: <4F742D3B.2060904@redhat.com>
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.
next prev parent reply other threads:[~2012-03-29 11:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 7:24 Question about removing memslots Benjamin Herrenschmidt
2012-03-28 9:37 ` Avi Kivity
2012-03-28 9:59 ` Benjamin Herrenschmidt
2012-03-28 10:05 ` Avi Kivity
2012-03-28 10:17 ` Benjamin Herrenschmidt
2012-03-28 10:51 ` Avi Kivity
2012-03-28 21:04 ` Benjamin Herrenschmidt
2012-03-29 9:36 ` Avi Kivity
2012-03-29 11:46 ` Benjamin Herrenschmidt [this message]
2012-03-29 13:49 ` Gerd Hoffmann
2012-03-29 5:15 ` Takuya Yoshikawa
2012-03-29 9:44 ` Avi Kivity
2012-03-29 15:21 ` Takuya Yoshikawa
2012-03-29 15:26 ` Avi Kivity
2012-03-29 15:35 ` Takuya Yoshikawa
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=1333021562.3010.11.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Alex.Williamson@redhat.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=scottwood@freescale.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