From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 22/23] Hack in dirty logging for VGA
Date: Wed, 08 Jul 2009 06:20:38 +0000 [thread overview]
Message-ID: <1247034038.6066.117.camel@pasglop> (raw)
In-Reply-To: <1246976262-4826-23-git-send-email-agraf@suse.de>
On Tue, 2009-07-07 at 18:48 +0300, Avi Kivity wrote:
> On 07/07/2009 05:17 PM, Alexander Graf wrote:
> > I haven't implemented dirty logging yet, but without things are just way too
> > slow. So for the time being I hacked in a dummy function that always tells
> > userspace we're dirty in VGA regions.
> >
> > Please don't apply this. This patch is for reference only.
> >
> >
>
> ia64 has the same problem; you can deal with this in userspace.
Well... also depending on what we are trying to emulate it might not be
worth at all presenting some kind of legacy VGA device. For example,
PowerMacs are physically incapable of generating the appropriate cycles
on the bus.
We are probably better off exposing pseudo PCI graphics device that is
reflected by a display node in the device-tree with enough information
populated there for offb to be able to pick it up initially, and then
have the option of paravirt drivers for accelerating it or making it
capable of switching modes etc... That's pretty much what we did with
MacOnLinux in fact.
Also, MOL kept track of dirtied pages in the fb as well to speed up
refresh.
Cheers,
Ben.
next prev parent reply other threads:[~2009-07-08 6:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 14:17 [PATCH 22/23] Hack in dirty logging for VGA Alexander Graf
2009-07-07 15:48 ` Avi Kivity
2009-07-07 15:53 ` Alexander Graf
2009-07-08 6:20 ` Benjamin Herrenschmidt [this message]
2009-07-08 7:39 ` Alexander Graf
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=1247034038.6066.117.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=kvm-ppc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.