From: "Hervé Poussineau" <hpoussin@reactos.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/8] memory: remove old_portio usage
Date: Tue, 18 Jun 2013 20:09:04 +0200 [thread overview]
Message-ID: <51C0A240.3040002@reactos.org> (raw)
In-Reply-To: <51C070D9.2050007@siemens.com>
Jan Kiszka a écrit :
> On 2013-06-17 22:39, Hervé Poussineau wrote:
>> Jan Kiszka a écrit :
>>> On 2013-06-17 09:32, Paolo Bonzini wrote:
>>>> Il 16/06/2013 20:20, Hervé Poussineau ha scritto:
>>>>> Hervé Poussineau a écrit :
>>>>>> These proposed patches aim at removing the .old_portio member of
>>>>>> MemoryRegionOps structure, and replacing their usage by .read/.write
>>>>>> handlers.
>>>>> Ping.
>>>> Jan has patches that do something similar, so I was hoping he'd look at it.
>>>>
>>>> Jan, are you back from vacation? :)
>>> Yes, and that is the problem. ;)
>>>
>>> >From a quick glance, I'm a bit skeptical, Hervé, that your patches are
>>> addressing all corner cases like mine. Did you see
>>> http://thread.gmane.org/gmane.comp.emulators.qemu/210188?
>>>
>>> Jan
>>>
>> My patches are less intrusive than yours, because they are probably less
>> complex. They don't change subpage handling, they don't remove the
>> register_ioport_*, and they don't move ioport handling to memory core.
>>
>> However, my patches do not add a new base address field in MemoryRegion,
>> and also simplify cpu_in/out to be simply a call to
>> address_space_read/write (like yours).
>>
>> I don't really care whatever way is chosen. I'm only interested to be
>> able to put I/O address space into memory space, so I can improve PReP
>> emulation.
>
> Refactorings like the subpage changes are required to break up the BQL
> also for PIO dispatching. So we need the complete rework. But, of
> course, I'm open for improvement suggestions.
>
> I'm planning to rebase my series on top of Paolo's changes soon and will
> then post. Would you mind rebasing what you need additionally on top of
> that?
Not a problem.
Moreover, with your patches, if devices registering ports with portio_*
functions can be added in the system memory address space, it will be
enough for me, and I'll happily drop my patches.
Hervé
next prev parent reply other threads:[~2013-06-18 18:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 17:43 [Qemu-devel] [PATCH v2 0/8] memory: remove old_portio usage Hervé Poussineau
2013-06-08 17:43 ` [Qemu-devel] [PATCH v2 1/8] isa: fix documentation of isa_register_portio_list Hervé Poussineau
2013-06-08 17:44 ` [Qemu-devel] [PATCH v2 2/8] memory: handle old_portio accesses in MMIO path Hervé Poussineau
2013-06-08 17:44 ` [Qemu-devel] [PATCH v2 3/8] ioport: register memory regions for I/O port lists Hervé Poussineau
2013-06-08 17:44 ` [Qemu-devel] [PATCH v2 4/8] memory: remove code dealing with old_portio Hervé Poussineau
2013-06-08 17:44 ` [Qemu-devel] [PATCH v2 5/8] ioport: reimplement cpu_in/cpu_out using address_space_rw Hervé Poussineau
2013-06-08 17:44 ` [Qemu-devel] [PATCH v2 6/8] ppc: simplify access to PReP I/O region Hervé Poussineau
2013-06-08 17:44 ` [Qemu-devel] [PATCH v2 7/8] PPC: pseries: Remove hack for PIO window Hervé Poussineau
2013-06-08 17:44 ` [Qemu-devel] [PATCH v2 8/8] isa_mmio: simplify access to system I/O region Hervé Poussineau
2013-06-16 18:20 ` [Qemu-devel] [PATCH v2 0/8] memory: remove old_portio usage Hervé Poussineau
2013-06-17 7:32 ` Paolo Bonzini
2013-06-17 7:43 ` Jan Kiszka
2013-06-17 20:39 ` Hervé Poussineau
2013-06-18 14:38 ` Jan Kiszka
2013-06-18 18:09 ` Hervé Poussineau [this message]
2013-06-21 18:11 ` Jan Kiszka
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=51C0A240.3040002@reactos.org \
--to=hpoussin@reactos.org \
--cc=jan.kiszka@siemens.com \
--cc=pbonzini@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.