qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RfC PATCH] spice: add qxl device
Date: Wed, 01 Sep 2010 10:45:53 +0200	[thread overview]
Message-ID: <4C7E12C1.8000806@redhat.com> (raw)
In-Reply-To: <4C7D0026.2060608@codemonkey.ws>

   Hi,

>> Signed-off-by: Gerd Hoffmann<kraxel@redhat.com>
>
> I've taken a quick look and have a few questions.
>
> Does this work without libspice (I think no)?

Correct, it needs libspice.  Even in case you'll use qxl with sdl/vnc 
libspice is needed to do the rendering.

> Why does spice need to perform arbitrary gpa -> hva conversions?
> Shouldn't everything happen within video ram?

Hmm, guess I should write up docs/qxl.txt explaining a few concepts.

QXL uses memory slots for addressing.  The guest specifies the address 
of some object (command, command data such as bitmaps, surfaces, ...) 
using a slot+offset tuple.

Memory slots are created by the guest.  qxl checks the request.  The 
allowed memory range covers the two pci slots at the moment.  If the 
checks pass qxl informs the spice server about the new slot and the 
location in qemu's address space so spice server can follow those 
references when parsing the qxl commands.

In a few places qxl needs to look at the commands itself, then it needs 
to do the memory slot lookup as well of course.  qxl_phys2virt does 
that, maybe I should rename that to qxl_memslot_lookup() or something 
simliar to make more clear what it actually does.

cheers
   Gerd

      reply	other threads:[~2010-09-01  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 10:53 [Qemu-devel] [RfC PATCH] spice: add qxl device Gerd Hoffmann
2010-08-31 11:29 ` malc
2010-08-31 13:14 ` Anthony Liguori
2010-09-01  8:45   ` Gerd Hoffmann [this message]

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=4C7E12C1.8000806@redhat.com \
    --to=kraxel@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).