qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Erlon Cruz <erlon.cruz@br.flextronics.com>
Cc: "Erlon R. Cruz" <erlon.cruz@fit-tecnologia.org.br>,
	"Fabiano Fidêncio" <fabiano@fidencio.org>,
	"Fabiano Fidêncio" <fabiano.fidencio@fit-tecnologia.org.br>,
	"Rafael F. Santos" <fonsecasantos.rafael@gmail.com>,
	qemu-devel@nongnu.org, alevy@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/4] qxl: split qxl functions in common and pci files
Date: Mon, 27 Aug 2012 08:05:54 +0200	[thread overview]
Message-ID: <503B0E42.4080809@redhat.com> (raw)
In-Reply-To: <1345835677-23371-3-git-send-email-erlon.cruz@br.flextronics.com>

On 08/24/12 21:14, Erlon Cruz wrote:
> From: Fabiano Fidêncio <fabiano@fidencio.org>
> 
> This commit splits qxl functions into common functions (located in
> qxl.c) and pci-specific functions (located in qxl-pci.c).
> All prototypes are being kept in qxl.h, as common MACROS and inline
> functions. Moreover, this commit is exposing a lot of APIs, don't know
> if it's the correct way to do it, but it was the only way that we saw to
> do it.

Try enabling rename detection for this one (git format-patch -M).

> diff --git a/hw/qxl.h b/hw/qxl.h
> index f25e341..516e7da 100644
> --- a/hw/qxl.h
> +++ b/hw/qxl.h
> @@ -143,6 +143,44 @@ typedef struct QXLDevice {
>          }                                                               \
>      } while (0)
>  
> +/*
> + * NOTE: SPICE_RING_PROD_ITEM accesses memory on the pci bar and as
> + * such can be changed by the guest, so to avoid a guest trigerrable
> + * abort we just qxl_set_guest_bug and set the return to NULL. Still
> + * it may happen as a result of emulator bug as well.
> + */

Why these are here and not in qxl-pci.c?

> +void init_qxl_rom(QXLDevice *d);
> +void init_qxl_ram(QXLDevice *d);

Same question.

> +void interface_get_init_info(QXLInstance *sin, QXLDevInitInfo *info);
> +int interface_get_command(QXLInstance *sin, struct QXLCommandExt *ext);
> +int interface_req_cmd_notification(QXLInstance *sin);
> +void interface_release_resource(QXLInstance *sin, struct QXLReleaseInfoExt ext);
> +int interface_get_cursor_command(QXLInstance *sin, struct QXLCommandExt *ext);
> +int interface_req_cursor_notification(QXLInstance *sin);
> +void interface_notify_update(QXLInstance *sin, uint32_t update_id);
> +int interface_flush_resources(QXLInstance *sin);
> +void interface_update_area_complete(QXLInstance *sin, uint32_t surface_id, QXLRect *dirty, uint32_t num_updated_rects);
> +void interface_async_complete(QXLInstance *sin, uint64_t cookie_token);
> +ram_addr_t qxl_rom_size(void);

Same question.

I'd expect at least some of these having a virtio-specific
implementation.  interface_get_command() for example, which gets a qxl
command from the ring ...

cheers,
  Gerd

  reply	other threads:[~2012-08-27  6:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 19:14 [Qemu-devel] Implementing qxl-virtio on QEMU Erlon Cruz
2012-08-24 19:14 ` [Qemu-devel] [PATCH 1/4] qxl: create a qxl common struct! Erlon Cruz
2012-08-27  5:51   ` Gerd Hoffmann
2012-08-24 19:14 ` [Qemu-devel] [PATCH 2/4] qxl: split qxl functions in common and pci files Erlon Cruz
2012-08-27  6:05   ` Gerd Hoffmann [this message]
2012-08-24 19:14 ` [Qemu-devel] [PATCH 3/4] qxl: implement VirtIO QXL (dummy) device support Erlon Cruz
2012-08-24 19:14 ` [Qemu-devel] [PATCH 4/4] qxl: introducing virtio-qxl Erlon Cruz
2012-08-27  6:08   ` Gerd Hoffmann
2012-08-27  6:08 ` [Qemu-devel] Implementing qxl-virtio on QEMU Gerd Hoffmann
2012-09-11 10:28   ` Gerd Hoffmann

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=503B0E42.4080809@redhat.com \
    --to=kraxel@redhat.com \
    --cc=alevy@redhat.com \
    --cc=erlon.cruz@br.flextronics.com \
    --cc=erlon.cruz@fit-tecnologia.org.br \
    --cc=fabiano.fidencio@fit-tecnologia.org.br \
    --cc=fabiano@fidencio.org \
    --cc=fonsecasantos.rafael@gmail.com \
    --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).