From: "Andreas Färber" <afaerber@suse.de>
To: "Hervé Poussineau" <hpoussin@reactos.org>
Cc: "lmr@redhat.com" <lmr@redhat.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [RFC 0/8] Remove old_portio usage
Date: Thu, 03 Jan 2013 00:32:07 +0100 [thread overview]
Message-ID: <50E4C377.1080205@suse.de> (raw)
In-Reply-To: <1356276769-7357-1-git-send-email-hpoussin@reactos.org>
Am 23.12.2012 16:32, schrieb Hervé Poussineau:
> These proposed patches aim at removing the .old_portio member of
> MemoryRegionOps structure, and replacing their usage by .read/.write
> handlers.
>
> Patches 2 to 6 are already ready to be committed.
In lack of a memory maintainer, I'll volunteer for reviewing those
portio conversions.
> However, patches 7 and 8 depend of patch 1, where a better solution
> needs to be found.
As for finding a solution to the bochs debug ports, can you resubmit
this series with the commit'able patches first, marked PATCH, and append
a proposal merging Gerd's, Lucas' and your QOM'ified debug device? Then
we can get the easy parts merged, and Anthony can ack/nack/timeout the
rest. :)
Regards,
Andreas
>
> That way, faked I/O address space can be removed from architectures
> which don't have it (MIPS, PowerPC...), and commits like
> a178274efabcbbc5d44805b51def874e47051325 ("PPC: pseries: Remove hack
> for PIO window") can be reapplied.
>
> Hervé Poussineau (8):
> pc: disable bochs bios debug ports (do not apply!)
> xen_platform: do not use old_portio-style callbacks
> uhci: do not use old_portio-style callbacks
> acpi-piix4: do not use old_portio-style callbacks
> vga/qxl: do not use portio_list_init/portio_list_add
> isa: use memory regions instead of portio_list_* functions
> ioport: remove now useless portio_list_* functions
> memory: remove old_portio-style callbacks support
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-01-02 23:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-23 15:32 [Qemu-devel] [RFC 0/8] Remove old_portio usage Hervé Poussineau
2012-12-23 15:32 ` [Qemu-devel] [RFC 1/8] pc: disable bochs bios debug ports (do not apply!) Hervé Poussineau
2012-12-23 15:32 ` [Qemu-devel] [RFC 2/8] xen_platform: do not use old_portio-style callbacks Hervé Poussineau
2012-12-23 15:32 ` [Qemu-devel] [RFC 3/8] uhci: " Hervé Poussineau
2013-01-03 14:09 ` Gerd Hoffmann
2012-12-23 15:32 ` [Qemu-devel] [RFC 4/8] acpi-piix4: " Hervé Poussineau
2012-12-23 15:32 ` [Qemu-devel] [RFC 5/8] vga/qxl: do not use portio_list_init/portio_list_add Hervé Poussineau
2012-12-23 15:32 ` [Qemu-devel] [RFC 6/8] isa: use memory regions instead of portio_list_* functions Hervé Poussineau
2012-12-23 15:32 ` [Qemu-devel] [RFC 7/8] ioport: remove now useless " Hervé Poussineau
2012-12-23 15:32 ` [Qemu-devel] [RFC 8/8] memory: remove old_portio-style callbacks support Hervé Poussineau
2013-01-02 23:32 ` Andreas Färber [this message]
2013-01-03 14:05 ` [Qemu-devel] [RFC 0/8] Remove old_portio usage 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=50E4C377.1080205@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=hpoussin@reactos.org \
--cc=kraxel@redhat.com \
--cc=lmr@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 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).