All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/4] memory: make memory API parsable by gtkdoc-scan
Date: Wed, 14 Dec 2011 23:23:34 +0100	[thread overview]
Message-ID: <4EE921E6.9070700@weilnetz.de> (raw)
In-Reply-To: <4EE91A7E.3060302@codemonkey.ws>

Am 14.12.2011 22:51, schrieb Anthony Liguori:
>
> Look carefully at:
>
> http://qemu.weilnetz.de/gtkdoc/QEMU-Memory-API.html#MemoryRegionOps
>
> vs:
>
> http://wiki.qemu.org/docs-internal/QEMU-Memory-API.html#MemoryRegionOps
>
> There's a significant difference :-)
>
> Regards,
>
> Anthony Liguori

I tried the following declaration:

typedef struct sMemoryRegionOps {
     uint64_t (*read)(void *opaque,
                      target_phys_addr_t addr,
                      unsigned size);
     void (*write)(void *opaque,
                   target_phys_addr_t addr,
                   uint64_t data,
                   unsigned size);

     enum device_endian endianness;

     MemoryRegionGuestConstraints valid;
     MemoryRegionInternalConstraints impl;

     const MemoryRegionPortio *old_portio;
     const MemoryRegionMmio old_mmio;
} MemoryRegionOps;

See the result here:
http://qemu.weilnetz.de/gtkdoc4/QEMU-Memory-API.html#MemoryRegionOps

Regards,
Stefan Weil

  reply	other threads:[~2011-12-14 22:24 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 16:20 [Qemu-devel] [PATCH 0/4] GTK-DOC build integration Anthony Liguori
2011-12-14 16:20 ` [Qemu-devel] [PATCH 1/4] memory: make memory API parsable by gtkdoc-scan Anthony Liguori
2011-12-14 16:34   ` malc
2011-12-14 16:55     ` Anthony Liguori
2011-12-14 17:11       ` Peter Maydell
2011-12-14 17:19         ` Anthony Liguori
2011-12-14 17:26           ` Peter Maydell
2011-12-14 18:00             ` Anthony Liguori
2011-12-14 17:55           ` Stefan Weil
2011-12-15  9:20             ` Avi Kivity
2011-12-15 13:35               ` Anthony Liguori
2011-12-14 18:54     ` Stefan Weil
2011-12-14 19:03       ` Anthony Liguori
2011-12-14 20:48         ` Stefan Weil
2011-12-14 20:54           ` Anthony Liguori
2011-12-14 21:26             ` Stefan Weil
2011-12-14 21:51               ` Anthony Liguori
2011-12-14 22:23                 ` Stefan Weil [this message]
2011-12-14 22:37                   ` Anthony Liguori
2011-12-14 20:23       ` Eric Blake
2011-12-14 20:43         ` malc
2011-12-14 20:49         ` Anthony Liguori
2011-12-14 16:20 ` [Qemu-devel] [PATCH 2/4] docs: add build infrastructure for gtkdocs Anthony Liguori
2011-12-15  9:37   ` Avi Kivity
2011-12-15 10:06     ` Stefan Weil
2011-12-15 13:30     ` Anthony Liguori
2011-12-15 13:43       ` Avi Kivity
2011-12-15 14:10         ` Anthony Liguori
2011-12-16  5:01       ` Andreas Färber
2011-12-14 16:20 ` [Qemu-devel] [PATCH 3/4] memory: update documentation to be in gtk-doc format Anthony Liguori
2011-12-15  9:26   ` Avi Kivity
2011-12-15 13:33     ` Anthony Liguori
2011-12-15 13:44       ` Avi Kivity
2011-12-14 16:20 ` [Qemu-devel] [PATCH 4/4] memory: move header into include/ and add to QEMU docs Anthony Liguori
2011-12-15  9:24   ` Avi Kivity
2011-12-15 13:34     ` Anthony Liguori
2011-12-15 13:45       ` Avi Kivity
2011-12-15 14:12         ` Anthony Liguori

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=4EE921E6.9070700@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.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 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.