Can you tell us why mpic should be in kernel? Is it used often by modern guests or may be they prefer MSI for interrupt delivery (hmm may be MSIs are delivered through mpic too)? On x86 we actually would've preferred to move PIC/IOAPIC form the kernel and leave only LAPIC there (but for historical reasons creation of PIC/IOAPIC/LAPIC are bundled together) hence my question.
On Wed, Feb 13, 2013 at 11:49:14PM -0600, Scott Wood wrote: > Scott Wood (6): > kvm: add device control API > kvm/ppc: add a notifier chain for vcpu creation/destruction. > kvm/ppc/mpic: import hw/openpic.c from QEMU > kvm/ppc/mpic: remove some obviously unneeded code > kvm/ppc/mpic: adapt to kernel style and environment > kvm/ppc/mpic: in-kernel MPIC emulation > > Documentation/virtual/kvm/api.txt | 76 ++ > Documentation/virtual/kvm/devices/README | 1 + > Documentation/virtual/kvm/devices/mpic.txt | 36 + > arch/powerpc/include/asm/kvm_host.h | 9 +- > arch/powerpc/include/asm/kvm_ppc.h | 4 + > arch/powerpc/kvm/Kconfig | 5 + > arch/powerpc/kvm/Makefile | 2 + > arch/powerpc/kvm/booke.c | 10 +- > arch/powerpc/kvm/mpic.c | 1890 > ++++++++++++++++++++++++++++ > arch/powerpc/kvm/powerpc.c | 31 +- > include/linux/kvm_host.h | 44 +- > include/uapi/linux/kvm.h | 34 + > virt/kvm/kvm_main.c | 141 +++ > 13 files changed, 2268 insertions(+), 15 deletions(-) > create mode 100644 Documentation/virtual/kvm/devices/README > create mode 100644 Documentation/virtual/kvm/devices/mpic.txt > create mode 100644 arch/powerpc/kvm/mpic.c > > -- > 1.7.9.5 > > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
