From: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, patches@apm.com, robherring2@gmail.com,
kvmarm@lists.cs.columbia.edu, christoffer.dall@linaro.org,
Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
Subject: [Qemu-devel] [RFC PATCH V4 0/6] PSCI v0.2 support for KVM ARM/ARM64
Date: Mon, 5 May 2014 14:27:08 +0530 [thread overview]
Message-ID: <1399280234-25036-1-git-send-email-pranavkumar@linaro.org> (raw)
This patchset adds the QEMU side changes for providing PSCI v0.2 to VM.
ChangeLog:
V4:
- Rebase this patch against v11 patchset for in-kernel PSCI v0.2 emulation
(http://www.spinics.net/lists/kvm-arm/msg09182.html)
- Used PSCI 0.2 DT bindings for linux kernel.
(http://www.spinics.net/lists/arm-kernel/msg326044.html).
V3:
- Rebase this patchset against v8 patchset for in-kernel PSCI v0.2 emulation
(http://www.spinics.net/lists/kvm-arm/msg08780.html)
- Added common kvm_arm_vcpu_init() function for kvm arm and kvm arm64
V2:
- Rebase this patchset against v6 patchset for in-kernel PSCI v0.2 emulation
(http://www.spinics.net/lists/arm-kernel/msg319037.html)
- Handle KVM_EXIT_SYSTEM_EVENT in kvm-all.c:kvm_cpu_exec()
- Drop change in kvm_arm_get_host_cpu_features()
- Improve comments and description of kvm_arch_reset_vcpu() implementation
V1:
- Initial RFC patchset
Pranavkumar Sawargaonkar (6):
linux-headers: Update KVM headers from linux-3.16-rc1
kvm: Handle exit reason KVM_EXIT_SYSTEM_EVENT
target-arm: Enable KVM_ARM_VCPU_PSCI_0_2 feature when possible
hw/arm/virt: Use PSCI v0.2 compatible when kernel supports it
target-arm: Common kvm_arm_vcpu_init() for KVM ARM and KVM ARM64
target-arm: Implement kvm_arch_reset_vcpu() for KVM ARM64
hw/arm/virt.c | 16 +++++---
kvm-all.c | 16 ++++++++
linux-headers/asm-arm/kvm.h | 10 +++--
linux-headers/asm-arm64/kvm.h | 10 +++--
linux-headers/linux/kvm.h | 27 ++++++++++++-
linux-headers/linux/psci.h | 90 +++++++++++++++++++++++++++++++++++++++++
target-arm/kvm.c | 23 +++++++++++
target-arm/kvm32.c | 15 ++-----
target-arm/kvm64.c | 23 ++++++-----
target-arm/kvm_arm.h | 14 +++++++
10 files changed, 206 insertions(+), 38 deletions(-)
create mode 100644 linux-headers/linux/psci.h
--
1.7.9.5
next reply other threads:[~2014-05-05 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 8:57 Pranavkumar Sawargaonkar [this message]
2014-05-05 8:57 ` [Qemu-devel] [RFC PATCH V4 1/6] linux-headers: Update KVM headers from linux-3.16-rc1 Pranavkumar Sawargaonkar
2014-05-06 18:44 ` Peter Maydell
2014-05-05 8:57 ` [Qemu-devel] [RFC PATCH V4 2/6] kvm: Handle exit reason KVM_EXIT_SYSTEM_EVENT Pranavkumar Sawargaonkar
2014-05-05 8:57 ` [Qemu-devel] [RFC PATCH V4 3/6] target-arm: Enable KVM_ARM_VCPU_PSCI_0_2 feature when possible Pranavkumar Sawargaonkar
2014-05-05 8:57 ` [Qemu-devel] [RFC PATCH V4 4/6] hw/arm/virt: Use PSCI v0.2 compatible when kernel supports it Pranavkumar Sawargaonkar
2014-05-05 14:06 ` Rob Herring
2014-05-05 14:09 ` Rob Herring
2014-05-05 14:43 ` Peter Maydell
2014-05-06 5:24 ` Pranavkumar Sawargaonkar
2014-05-06 14:58 ` Rob Herring
2014-05-06 14:59 ` Peter Maydell
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=1399280234-25036-1-git-send-email-pranavkumar@linaro.org \
--to=pranavkumar@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=patches@apm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=robherring2@gmail.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).