public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	airlied@linux.ie, Matt Turner <mattst88@gmail.com>
Subject: Re: [PATCH] drm: Add a driver for kvm emulated Cirrus
Date: Mon, 18 Apr 2011 22:20:13 +0100	[thread overview]
Message-ID: <20110418212013.GA1778@srcf.ucam.org> (raw)
In-Reply-To: <20110418220306.7799d850@lxorguk.ukuu.org.uk>

On Mon, Apr 18, 2011 at 10:03:06PM +0100, Alan Cox wrote:
> So has this been benchmarked - intuitively I'd agree and expect that a
> shadowfb driver ought to give best performance.

No, but it's noticably nicer to use under virt-manager. I'll try to come 
up with some numbers.

> > +/* Map the framebuffer from the card and configure the core */
> > +static int cirrus_vram_init(struct cirrus_device *cdev)
> > +{
> > +	int ret;
> > +
> > +	/* BAR 0 is VRAM */
> > +	cdev->mc.vram_base = pci_resource_start(cdev->ddev->pdev, 0);
> > +	/* We have 4MB of VRAM */
> > +	cdev->mc.vram_size = 4 * 1024 * 1024;
> 
> For real hardware at least you should check that the pci resource is at
> least 4Mb long before doing this, otherwise the resulting progression in
> the fail case is that you map some other device into user address space,
> which isn't good!

True. The PCI table is restrictive enough that it won't bind to real 
hardware, so I don't know if it's worth it to be paranoid.

> > +static void cirrus_encoder_mode_set(struct drm_encoder *encoder,
> > +				struct drm_display_mode *mode,
> > +				struct drm_display_mode *adjusted_mode)
> > +{
> > +	struct drm_device *dev = encoder->dev;
> > +	struct cirrus_device *cdev = dev->dev_private;
> > +
> > +	unsigned char tmp;
> > +
> > +	switch (encoder->crtc->fb->bits_per_pixel) {
> > +	case 8:
> > +		tmp = 0x0;
> > +		break;
> > +	case 16:
> > +		/* Enable 16 bit mode */
> > +		WREG_HDR(0x01);
> 
> If you switch back from 16 does this not need clearing ?

Nope. qemu just looks at this to distinguish between 15 and 16 bit, and 
I've no intention of supporting 15 bit...

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2011-04-18 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18 20:04 [PATCH] drm: Add a driver for kvm emulated Cirrus Matthew Garrett
2011-04-18 20:26 ` Matt Turner
2011-04-18 21:03 ` Alan Cox
2011-04-18 21:20   ` Matthew Garrett [this message]
2011-04-19 17:38     ` Matthew Garrett
2011-08-02 21:29 ` Stefan Lippers-Hollmann

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=20110418212013.GA1778@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=airlied@linux.ie \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattst88@gmail.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