From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: agraf@suse.de, aneesh.kumar@linux.vnet.ibm.com
Cc: paulus@samba.org, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/4] target-ppc: htab fixes
Date: Mon, 17 Feb 2014 14:22:14 +0100 [thread overview]
Message-ID: <20140217132213.25977.96973.stgit@bahia.local> (raw)
Hi,
This is a new tentative for the patches 2/5 to 5/5 from the "target-ppc: Add
support for dumping guest memory using qemu gdb server" patchset:
https://lists.nongnu.org/archive/html/qemu-ppc/2014-01/msg00380.html
All patches have been rebased on the current ppc-next head (72c798d7dccc).
To ensure proper bisectability, the following was verified for each individual
patch:
•- 32 and 64 bit build of ppc-softmmu and ppc64-softmmu (fedora 19 ppc64)
•- 64 bit pseries guest with KVM on a POWER7 host (fedora 19 ppc64)
•- 64 bit pseries guest with 64 bit TCG on a x86_64 host (fedora 19 ppc64)
•- 64 bit pseries guest with 32 bit TCG on a x86_64 host (fedora 19 ppc64)
•- 32 bit mac99 guest with 64 bit TCG on a x86_64 host (wheezy ppc)
•- 32 bit mac99 guest with 32 bit TCG on a x86_64 host (wheezy ppc)
Alex,
This should address all the requirements you expressed in your last mail.
Please tell me if something is missing.
Best regards.
---
Aneesh Kumar K.V (4):
target-ppc: Fix htab_mask calculation
target-ppc: Fix page table lookup with kvm enabled
target-ppc: Change the hpte store API
target-ppc: Update ppc_hash64_store_hpte to support updating in-kernel htab
hw/ppc/spapr.c | 9 ++++
hw/ppc/spapr_hcall.c | 81 ++++++++++++++++++++++---------------
target-ppc/cpu.h | 1
target-ppc/kvm.c | 93 ++++++++++++++++++++++++++++++++++++++++++
target-ppc/kvm_ppc.h | 29 +++++++++++++
target-ppc/machine.c | 11 +++--
target-ppc/misc_helper.c | 4 +-
target-ppc/mmu-hash64.c | 101 +++++++++++++++++++++++++++++++++++++++-------
target-ppc/mmu-hash64.h | 47 ++++++++-------------
target-ppc/mmu_helper.c | 3 +
10 files changed, 293 insertions(+), 86 deletions(-)
--
Greg
next reply other threads:[~2014-02-17 13:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 13:22 Greg Kurz [this message]
2014-02-17 13:22 ` [Qemu-devel] [PATCH 1/4] target-ppc: Fix htab_mask calculation Greg Kurz
2014-02-17 13:22 ` [Qemu-devel] [PATCH 2/4] target-ppc: Fix page table lookup with kvm enabled Greg Kurz
2014-02-17 13:22 ` [Qemu-devel] [PATCH 3/4] target-ppc: Change the hpte store API Greg Kurz
2014-02-17 13:22 ` [Qemu-devel] [PATCH 4/4] target-ppc: Update ppc_hash64_store_hpte to support updating in-kernel htab Greg Kurz
2014-02-20 17:52 ` [Qemu-devel] [PATCH 0/4] target-ppc: htab fixes (V2) Greg Kurz
2014-02-20 17:52 ` [Qemu-devel] [PATCH 1/4] target-ppc: Fix htab_mask calculation Greg Kurz
2014-02-20 17:52 ` [Qemu-devel] [PATCH 2/4] target-ppc: Fix page table lookup with kvm enabled Greg Kurz
2014-02-20 17:52 ` [Qemu-devel] [PATCH 3/4] target-ppc: Change the hpte store API Greg Kurz
2014-02-20 17:52 ` [Qemu-devel] [PATCH 4/4] target-ppc: Update ppc_hash64_store_hpte to support updating in-kernel htab Greg Kurz
2014-02-25 14:44 ` [Qemu-devel] [PATCH 0/4] target-ppc: htab fixes (V2) Alexander Graf
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=20140217132213.25977.96973.stgit@bahia.local \
--to=gkurz@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).