[PATCH RFC] KVM: PPC: Book3S HV: Reserve POWER8 space in get/set_one_reg

2013-08-30 Thread Michael Neuling
Alex, This reserves space in get/set_one_reg ioctl for the extra guest state needed for POWER8. It doesn't implement these at all, it just reserves them so that the ABI is defined now. A few things to note here: - POWER8 has 6 PMCs and an additional 2 SPMCs for the supervisor. Here I'm

Re: [PATCH v9 00/13] KVM: PPC: IOMMU in-kernel handling of VFIO

2013-08-30 Thread Alexey Kardashevskiy
On 08/28/2013 06:37 PM, Alexey Kardashevskiy wrote: This accelerates VFIO DMA operations on POWER by moving them into kernel. This depends on VFIO external API patch which is on its way to upstream. Changes: v9: * replaced the link logical bus number to IOMMU group ioctl to KVM with a

Re: [PULL 00/19] ppc patch queue 2013-08-29

2013-08-30 Thread Gleb Natapov
On Thu, Aug 29, 2013 at 12:21:58PM +0200, Alexander Graf wrote: Hi Paolo / Gleb, This is my current patch queue for ppc. Please pull. Pulled, thanks. Changes include: - Book3S HV: CMA based memory allocator for linear memory - A few bug fixes Alex The following changes

Re: [PATCH RFC] KVM: PPC: Book3S HV: Reserve POWER8 space in get/set_one_reg

2013-08-30 Thread Alexander Graf
On 30.08.2013, at 08:09, Michael Neuling wrote: Alex, This reserves space in get/set_one_reg ioctl for the extra guest state needed for POWER8. It doesn't implement these at all, it just reserves them so that the ABI is defined now. A few things to note here: - POWER8 has 6 PMCs

Re: [PATCH 14/23] KVM: PPC: Book3S PR: Delay disabling relocation-on interrupts

2013-08-30 Thread Alexander Graf
On 06.08.2013, at 06:23, Paul Mackerras wrote: When we are running a PR KVM guest on POWER8, we have to disable the new POWER8 feature of taking interrupts with relocation on, that is, of taking interrupts without disabling the MMU, because the SLB does not contain the normal kernel SLB

Re: [PATCH v9 00/13] KVM: PPC: IOMMU in-kernel handling of VFIO

2013-08-30 Thread Gleb Natapov
On Fri, Aug 30, 2013 at 08:26:54PM +1000, Alexey Kardashevskiy wrote: On 08/28/2013 06:37 PM, Alexey Kardashevskiy wrote: This accelerates VFIO DMA operations on POWER by moving them into kernel. This depends on VFIO external API patch which is on its way to upstream. Changes: v9:

Re: [PATCH RFC] KVM: PPC: Book3S HV: Reserve POWER8 space in get/set_one_reg

2013-08-30 Thread Michael Neuling
On Sat, Aug 31, 2013 at 8:17 AM, Benjamin Herrenschmidt b...@kernel.crashing.org wrote: On Fri, 2013-08-30 at 16:01 +0200, Alexander Graf wrote: - The TM state is offset bu 0x1000. Other than being bigger than the SPR space, it's fairly arbitrarily chose. Make it higher, just in

Re: [PATCH RFC] KVM: PPC: Book3S HV: Reserve POWER8 space in get/set_one_reg

2013-08-30 Thread Michael Neuling
On Sat, Aug 31, 2013 at 12:01 AM, Alexander Graf ag...@suse.de wrote: On 30.08.2013, at 08:09, Michael Neuling wrote: Alex, This reserves space in get/set_one_reg ioctl for the extra guest state needed for POWER8. It doesn't implement these at all, it just reserves them so that the ABI is

Re: [PATCH 14/23] KVM: PPC: Book3S PR: Delay disabling relocation-on interrupts

2013-08-30 Thread Paul Mackerras
On Fri, Aug 30, 2013 at 06:30:50PM +0200, Alexander Graf wrote: On 06.08.2013, at 06:23, Paul Mackerras wrote: When we are running a PR KVM guest on POWER8, we have to disable the new POWER8 feature of taking interrupts with relocation on, that is, of taking interrupts without disabling

Re: [PATCH 14/23] KVM: PPC: Book3S PR: Delay disabling relocation-on interrupts

2013-08-30 Thread Alexander Graf
On 31.08.2013, at 00:55, Paul Mackerras wrote: On Fri, Aug 30, 2013 at 06:30:50PM +0200, Alexander Graf wrote: On 06.08.2013, at 06:23, Paul Mackerras wrote: When we are running a PR KVM guest on POWER8, we have to disable the new POWER8 feature of taking interrupts with relocation on,

Re: [PATCH 14/23] KVM: PPC: Book3S PR: Delay disabling relocation-on interrupts

2013-08-30 Thread Paul Mackerras
On Sat, Aug 31, 2013 at 01:13:07AM +0200, Alexander Graf wrote: Oh, sorry to not be more explicit here. I meant the one that actually introduced the relocation-on handling: https://lists.ozlabs.org/pipermail/linuxppc-dev/2012-December/102355.html I can't find any trace of that in my