From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Richard Henderson <rth@twiddle.net>,
peterx@redhat.com, Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PATCH 0/3] cpu: suffix cpu address spaces with indexes
Date: Thu, 23 Nov 2017 17:23:30 +0800 [thread overview]
Message-ID: <20171123092333.16085-1-peterx@redhat.com> (raw)
I picked up Alexey's patch to fix pci address space names (which is
possibly lost on the list), and refactored cpu address spaces a bit
more. Now most of the address spaces (I believe some corner cases are
there) should have a valid and good name. I think this is pretty safe
even for 2.11, but I'm fine too to delay this to 2.12.
Please review, thanks.
Alexey Kardashevskiy (1):
pci: Initialize pci_dev->name before use
Peter Xu (2):
cpu: refactor cpu_address_space_init()
cpu: suffix cpu address spaces with cpu index
cpus.c | 5 +----
exec.c | 10 +++++++++-
hw/pci/pci.c | 2 +-
include/exec/exec-all.h | 6 ++++--
target/arm/cpu.c | 13 +++----------
target/i386/cpu.c | 10 ++--------
6 files changed, 20 insertions(+), 26 deletions(-)
--
2.14.3
next reply other threads:[~2017-11-23 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 9:23 Peter Xu [this message]
2017-11-23 9:23 ` [Qemu-devel] [PATCH 1/3] pci: Initialize pci_dev->name before use Peter Xu
2017-11-24 0:16 ` Alexey Kardashevskiy
2017-11-24 6:49 ` Peter Xu
2017-11-23 9:23 ` [Qemu-devel] [PATCH 2/3] cpu: refactor cpu_address_space_init() Peter Xu
2017-11-23 16:06 ` Paolo Bonzini
2017-11-24 7:12 ` Peter Xu
2017-11-23 9:23 ` [Qemu-devel] [PATCH 3/3] cpu: suffix cpu address spaces with cpu index Peter Xu
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=20171123092333.16085-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=aik@ozlabs.ru \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).