qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Stefano.Stabellini@eu.citrix.com, jan.kiszka@siemens.com,
	qemu-devel@nongnu.org, Julien Grall <julien.grall@citrix.com>,
	Avi Kivity <avi@redhat.com>,
	Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH V10 0/8] memory: unify ioport registration
Date: Mon, 26 Nov 2012 15:25:19 +0100	[thread overview]
Message-ID: <50B37BCF.5090205@redhat.com> (raw)
In-Reply-To: <50B232E5.4030302@suse.de>

On 11/25/12 16:01, Andreas Färber wrote:
> Am 25.11.2012 10:10, schrieb Avi Kivity:
>> On 09/19/2012 02:50 PM, Julien Grall wrote:
>>> This is the tenth version of patch series about ioport registration.
>>>
>>> Some part of QEMU still use register_ioport* functions to register ioport.
>>> These functions doesn't allow to use Memory Listener on it.
>>
>> Acked-by: Avi Kivity <avi@redhat.com>
> 
> Thanks, queued for the v1.4 merge window:
> https://github.com/afaerber/qemu-cpu/commits/memory-ioport

I'd like to veto the acpi/smbus bits of this series.  I've waded through
that last week from q35 point of view.  Alot of the memory region stuff
can be moved to acpi.c, and then easily be shared between piix4,
vt82c686 and the upcoming ich9.  See the "acpi: switch to memory api"
patch series posted last friday.

cheers.
  Gerd

  parent reply	other threads:[~2012-11-26 14:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 11:50 [Qemu-devel] [PATCH V10 0/8] memory: unify ioport registration Julien Grall
2012-09-19 11:50 ` [Qemu-devel] [PATCH V10 1/8] isa: add isa_address_space_io Julien Grall
2012-11-25 12:39   ` Andreas Färber
2012-09-19 11:50 ` [Qemu-devel] [PATCH V10 2/8] hw/apm.c: replace register_ioport* Julien Grall
2012-11-25 12:51   ` Andreas Färber
2012-11-27  0:10   ` Andreas Färber
2012-11-27 20:46     ` Jason Baron
2012-12-03 16:29       ` Julien Grall
2012-09-19 11:50 ` [Qemu-devel] [PATCH V10 3/8] smb: replace_register_ioport* Julien Grall
2012-09-19 11:50 ` [Qemu-devel] [PATCH V10 4/8] hw/acpi_piix4.c: replace register_ioport* Julien Grall
2012-09-19 11:50 ` [Qemu-devel] [PATCH V10 5/8] hw/cirrus_vga.c: " Julien Grall
2012-09-19 11:50 ` [Qemu-devel] [PATCH V10 6/8] hw/serial.c: " Julien Grall
2012-09-19 11:50 ` [Qemu-devel] [PATCH V10 7/8] hw/pc.c: " Julien Grall
2012-09-19 11:50 ` [Qemu-devel] [PATCH V10 8/8] hw/dma.c: " Julien Grall
2012-10-08 16:53 ` [Qemu-devel] [PATCH V10 0/8] memory: unify ioport registration Julien Grall
2012-11-24  1:09   ` Julien Grall
2012-11-25  9:10     ` Avi Kivity
2012-11-25  9:10 ` Avi Kivity
2012-11-25 12:42   ` Andreas Färber
2012-11-25 12:44     ` Avi Kivity
2012-11-25 15:01   ` Andreas Färber
2012-11-25 15:40     ` Avi Kivity
2012-11-25 16:00       ` Jan Kiszka
2012-11-25 22:33     ` Julien Grall
2012-11-26 14:25     ` Gerd Hoffmann [this message]
2012-11-27  1:14       ` Andreas Färber
2012-11-30 16:28         ` Julien Grall

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=50B37BCF.5090205@redhat.com \
    --to=kraxel@redhat.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=julien.grall@citrix.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).