[PATCH] KVM: PPC: fix suspicious use of conditional operator

This was signaled by a static code analysis tool. Signed-off-by: Laurentiu Tudor Reviewed-by: Scott Wood --- arch/powerpc/kvm/e500_mmu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/kvm/e500_mmu.c b/arch/powerpc/kvm/e500_mmu.c index 50860e9..29911a0 100644 --

Re: [PATCH] KVM: PPC: fix suspicious use of conditional operator

On 25.05.15 10:48, Laurentiu Tudor wrote: > This was signaled by a static code analysis tool. > > Signed-off-by: Laurentiu Tudor > Reviewed-by: Scott Wood Thanks, applied to kvm-ppc-queue. Alex -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to

Re: [PATCH] KVM: PPC: Remove PPC970 from KVM_BOOK3S_64_HV text in Kconfig

On 22.05.15 11:41, Thomas Huth wrote: > Since the PPC970 support has been removed from the kvm-hv kernel > module recently, we should also reflect this change in the help > text of the corresponding Kconfig option. > > Signed-off-by: Thomas Huth Thanks, applied to kvm-ppc-queue. Alex -- To u

Re: [PATCH] KVM: PPC: Remove PPC970 from KVM_BOOK3S_64_HV text in Kconfig

On 22.05.15 11:41, Thomas Huth wrote: > Since the PPC970 support has been removed from the kvm-hv kernel > module recently, we should also reflect this change in the help > text of the corresponding Kconfig option. > > Signed-off-by: Thomas Huth Thanks, applied to kvm-ppc-queue. Alex -- To un

Re: [PATCH] KVM: PPC: Fix warnings from sparse

On 22.05.15 09:25, Thomas Huth wrote: > When compiling the KVM code for POWER with "make C=1", sparse > complains about functions missing proper prototypes and a 64-bit > constant missing the ULL prefix. Let's fix this by making the > functions static or by including the proper header with the >

Re: [PATCH] KVM: PPC: check for lookup_linux_ptep() returning NULL

On 21.05.15 21:37, Scott Wood wrote: > On Thu, 2015-05-21 at 16:26 +0300, Laurentiu Tudor wrote: >> If passed a larger page size lookup_linux_ptep() >> may fail, so add a check for that and bail out >> if that's the case. >> This was found with the help of a static >> code analysis tool. >> >> Si

Re: [PATCH 1/1] KVM: PPC: Book3S: correct width in XER handling

On 20.05.15 07:26, Sam Bobroff wrote: > In 64 bit kernels, the Fixed Point Exception Register (XER) is a 64 > bit field (e.g. in kvm_regs and kvm_vcpu_arch) and in most places it is > accessed as such. > > This patch corrects places where it is accessed as a 32 bit field by a > 64 bit kernel. I

Re: [PATCH] KVM: PPC: add missing pt_regs initialization

On 18.05.15 14:44, Laurentiu Tudor wrote: > On this switch branch the regs initialization > doesn't happen so add it. > This was found with the help of a static > code analysis tool. > > Signed-off-by: Laurentiu Tudor > Cc: Scott Wood > Cc: Mihai Caraman Thanks, applied to kvm-ppc-queue. A

Re: [PATCH 1/1] KVM: PPC: Book3S: correct width in XER handling

On Mon, May 25, 2015 at 11:08:08PM +0200, Alexander Graf wrote: > > > On 20.05.15 07:26, Sam Bobroff wrote: > > In 64 bit kernels, the Fixed Point Exception Register (XER) is a 64 > > bit field (e.g. in kvm_regs and kvm_vcpu_arch) and in most places it is > > accessed as such. > > > > This patch

Re: [PATCH 1/1] KVM: PPC: Book3S: correct width in XER handling

On 26.05.15 02:14, Sam Bobroff wrote: > On Mon, May 25, 2015 at 11:08:08PM +0200, Alexander Graf wrote: >> >> >> On 20.05.15 07:26, Sam Bobroff wrote: >>> In 64 bit kernels, the Fixed Point Exception Register (XER) is a 64 >>> bit field (e.g. in kvm_regs and kvm_vcpu_arch) and in most places it i

[PATCH v2 1/1] KVM: PPC: Book3S: correct width in XER handling

In 64 bit kernels, the Fixed Point Exception Register (XER) is a 64 bit field (e.g. in kvm_regs and kvm_vcpu_arch) and in most places it is accessed as such. This patch corrects places where it is accessed as a 32 bit field by a 64 bit kernel. In some cases this is via a 32 bit load or store inst