From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>, qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org
Subject: [Qemu-devel] [PATCH v3 0/2] Type-safe ioport callbacks
Date: Wed, 17 Nov 2010 11:50:08 +0200 [thread overview]
Message-ID: <1289987410-466-1-git-send-email-avi@redhat.com> (raw)
A not-so-recent qemu -> qemu-kvm merge broke cpu hotplug without the compiler
complaining because of the type-unsafeness of the ioport callbacks. This
patchset adds a type-safe variant of ioport callbacks and coverts a sample
ioport. Converting the other 300-odd registrations is left as an excercise
to the community.
v3:
- define a common IORange that can also be used for mmio
- move start/length into IORange
- make access width a parameter of the access functions instead of
having a callback per access size
v2:
- const correctness
- avoid return void
Avi Kivity (2):
Type-safe ioport callbacks
piix4 acpi: convert io BAR to type-safe ioport callbacks
hw/acpi_piix4.c | 55 +++++++++++++++++++----------------------------
ioport.c | 64 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
ioport.h | 2 +
iorange.h | 30 +++++++++++++++++++++++++
4 files changed, 118 insertions(+), 33 deletions(-)
create mode 100644 iorange.h
--
1.7.3.1
next reply other threads:[~2010-11-17 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 9:50 Avi Kivity [this message]
2010-11-17 9:50 ` [Qemu-devel] [PATCH v3 1/2] Type-safe ioport callbacks Avi Kivity
2010-11-17 9:50 ` [Qemu-devel] [PATCH v3 2/2] piix4 acpi: convert io BAR to type-safe " Avi Kivity
2010-11-21 15:18 ` [Qemu-devel] [PATCH v3 0/2] Type-safe " 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=1289987410-466-1-git-send-email-avi@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--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).