From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
aik@ozlabs.ru, jan.kiszka@siemens.com, qemu-devel@nongnu.org,
qemulist@gmail.com, Avi Kivity <avi.kivity@gmail.com>,
stefanha@redhat.com, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH 00/40] Memory-related changes sneak peek for 1.6
Date: Tue, 07 May 2013 22:21:40 +0200 [thread overview]
Message-ID: <51896254.70901@redhat.com> (raw)
In-Reply-To: <CAFEAcA_nhkbUiF_q4jAsgiQGbBQ7_Qc-O1co-VKmBJdyoEG-kQ@mail.gmail.com>
Il 07/05/2013 20:51, Peter Maydell ha scritto:
> On 7 May 2013 15:16, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Patches 1-10 are small changes, some of them bugfixes for the IOMMU
>> portion of the patches.
>>
>> Patches 11-13 introduce three new address_space APIs and clean up
>> the dispatch logic a bit by removing memory_region_section_addr.
>>
>> Patches 14-22 introduce IOMMU memory regions, convert sPAPR to the
>> new API, and finally eliminate DMAContext in favor of AddressSpace.
>>
>> Patches 24-37 set an owner on all regions owned by hot-unpluggable
>> devices (and several others when that was easy), and add ref/unref
>> calls that keep the regions alive even if the owner is hot-unplugged.
>>
>> Patches 38-40 make memory_region_find safe for usage outside the BQL.
>
> I assume you're not going to try to get these all committed
> in one lump, by the way?
In as big a lump as possible, but not necessarily in one lump.
> I stopped reviewing after patch 22,
> since the BQL related stuff seems to still be under
> discussion.
Note that patch 37 is a fix for an existing bug (disk I/O to a
device-owned RAM area can corrupt QEMU if you unplug the device in
parallel), and it needs all the 13 previous patches unfortunately.
Only the last 3 are strictly for out-of-BQL operation.
Paolo
next prev parent reply other threads:[~2013-05-07 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 14:16 [Qemu-devel] [PATCH 00/40] Memory-related changes sneak peek for 1.6 Paolo Bonzini
2013-05-07 14:46 ` Peter Maydell
2013-05-07 14:54 ` Paolo Bonzini
2013-05-07 18:51 ` Peter Maydell
2013-05-07 20:21 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-07 14:16 Paolo Bonzini
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=51896254.70901@redhat.com \
--to=pbonzini@redhat.com \
--cc=aik@ozlabs.ru \
--cc=avi.kivity@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=jan.kiszka@siemens.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemulist@gmail.com \
--cc=stefanha@redhat.com \
/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).