linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: c.dall@virtualopensystems.com (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 00/10] KVM/ARM vGIC support
Date: Mon, 01 Oct 2012 05:12:50 -0400	[thread overview]
Message-ID: <20121001091244.49503.96318.stgit@ubuntu> (raw)

The following series implements support for the virtual generic
interrupt controller architecture for KVM/ARM.

This is an unmodified repost of the previously submitted series.

This patch series can also be pulled from:
    git://github.com/virtualopensystems/linux-kvm-arm.git
        branch: kvm-arm-v12-vgic

---

Marc Zyngier (10):
      ARM: KVM: Keep track of currently running vcpus
      ARM: KVM: Initial VGIC infrastructure support
      ARM: KVM: Initial VGIC MMIO support code
      ARM: KVM: VGIC distributor handling
      ARM: KVM: VGIC virtual CPU interface management
      ARM: KVM: VGIC interrupt injection
      ARM: KVM: VGIC control interface world switch
      ARM: KVM: VGIC initialisation code
      ARM: KVM: vgic: reduce the number of vcpu kick
      ARM: KVM: Add VGIC configuration option


 arch/arm/include/asm/kvm_arm.h  |   12 
 arch/arm/include/asm/kvm_host.h |   16 +
 arch/arm/include/asm/kvm_vgic.h |  301 +++++++++++
 arch/arm/kernel/asm-offsets.c   |   12 
 arch/arm/kvm/Kconfig            |    7 
 arch/arm/kvm/Makefile           |    1 
 arch/arm/kvm/arm.c              |  101 +++-
 arch/arm/kvm/interrupts.S       |    4 
 arch/arm/kvm/interrupts_head.S  |   68 ++
 arch/arm/kvm/mmu.c              |    3 
 arch/arm/kvm/vgic.c             | 1115 +++++++++++++++++++++++++++++++++++++++
 virt/kvm/kvm_main.c             |    5 
 12 files changed, 1640 insertions(+), 5 deletions(-)
 create mode 100644 arch/arm/include/asm/kvm_vgic.h
 create mode 100644 arch/arm/kvm/vgic.c

-- 

             reply	other threads:[~2012-10-01  9:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01  9:12 Christoffer Dall [this message]
2012-10-01  9:13 ` [PATCH v2 01/10] ARM: KVM: Keep track of currently running vcpus Christoffer Dall
2012-10-01  9:13 ` [PATCH v2 02/10] ARM: KVM: Initial VGIC infrastructure support Christoffer Dall
2012-10-01  9:13 ` [PATCH v2 03/10] ARM: KVM: Initial VGIC MMIO support code Christoffer Dall
2012-10-01  9:13 ` [PATCH v2 04/10] ARM: KVM: VGIC distributor handling Christoffer Dall
2012-10-01  9:13 ` [PATCH v2 05/10] ARM: KVM: VGIC virtual CPU interface management Christoffer Dall
2012-10-01  9:14 ` [PATCH v2 06/10] ARM: KVM: VGIC interrupt injection Christoffer Dall
2012-10-01  9:14 ` [PATCH v2 07/10] ARM: KVM: VGIC control interface world switch Christoffer Dall
2012-10-01  9:14 ` [PATCH v2 08/10] ARM: KVM: VGIC initialisation code Christoffer Dall
2012-10-02  9:24   ` Will Deacon
2012-10-02 10:25     ` Marc Zyngier
2012-10-02 17:55       ` Christoffer Dall
2012-10-02 18:31         ` [kvmarm] " Peter Maydell
2012-10-02 19:28           ` Will Deacon
2012-10-02 19:45             ` Peter Maydell
2012-10-03 10:02               ` Will Deacon
2012-10-03 15:05                 ` Christoffer Dall
2012-10-01  9:14 ` [PATCH v2 09/10] ARM: KVM: vgic: reduce the number of vcpu kick Christoffer Dall
2012-10-01  9:14 ` [PATCH v2 10/10] ARM: KVM: Add VGIC configuration option Christoffer Dall

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=20121001091244.49503.96318.stgit@ubuntu \
    --to=c.dall@virtualopensystems.com \
    --cc=linux-arm-kernel@lists.infradead.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).