[PATCH v2 1/1] KVM: arm64: Correctly handle the mmio faulting

Fixes: 6d674e28 ("KVM: arm/arm64: Properly handle faulting of device mappings") Suggested-by: Marc Zyngier Signed-off-by: Santosh Shukla --- v2: - Per Marc's suggestion - setting force_pte=true. - Rebased and tested for 5.10-rc1 commit: 3650b228 v1: https://lkml.org/lkml/2020/10/21/460 arch

[PATCH v2 0/1] KVM: arm64: fix the mmio faulting

gpa_t gpa = mem->guest_phys_addr + (vm_start - mem->userspace_addr); Thanks. Santosh [1] https://lkml.org/lkml/2020/10/23/310 [2] https://lkml.org/lkml/2020/10/21/460 Santosh Shukla (1): KVM: arm64: Correctly handle the mmio faulting arch/arm64/kvm/mmu.c | 1 + 1 file changed, 1 insertion(+) -- 2.7.4

[PATCH] KVM: arm64: Correctly handle the mmio faulting

vice. Linux tip: 583090b1 Fixes: 6d674e28 ("KVM: arm/arm64: Properly handle faulting of device mappings") Signed-off-by: Santosh Shukla --- arch/arm64/kvm/mmu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c index 3d26b47..

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

On Thu, Dec 31, 2015 at 9:11 PM, Alex Williamson wrote: > On Thu, 2015-12-31 at 15:03 +0530, Santosh Shukla wrote: >> On Tue, Dec 29, 2015 at 11:01 PM, Alex Williamson >> wrote: >> > On Tue, 2015-12-29 at 22:00 +0530, Santosh Shukla wrote: >> > > On Tue, De

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

On Thu, Dec 31, 2015 at 9:11 PM, Alex Williamson <alex.william...@redhat.com> wrote: > On Thu, 2015-12-31 at 15:03 +0530, Santosh Shukla wrote: >> On Tue, Dec 29, 2015 at 11:01 PM, Alex Williamson >> <alex.william...@redhat.com> wrote: >> > On Tue, 2015-12-29

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

On Tue, Dec 29, 2015 at 11:01 PM, Alex Williamson wrote: > On Tue, 2015-12-29 at 22:00 +0530, Santosh Shukla wrote: >> On Tue, Dec 29, 2015 at 9:50 PM, Arnd Bergmann wrote: >> > On Tuesday 29 December 2015 21:25:15 Santosh Shukla wrote: >> > > mistakenly added wrong

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

On Tue, Dec 29, 2015 at 11:01 PM, Alex Williamson <alex.william...@redhat.com> wrote: > On Tue, 2015-12-29 at 22:00 +0530, Santosh Shukla wrote: >> On Tue, Dec 29, 2015 at 9:50 PM, Arnd Bergmann <a...@arndb.de> wrote: >> > On Tuesday 29 December 2015

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

On Tue, Dec 29, 2015 at 9:50 PM, Arnd Bergmann wrote: > On Tuesday 29 December 2015 21:25:15 Santosh Shukla wrote: >> mistakenly added wrong email-id of alex, looping his correct one. >> >> On 29 December 2015 at 21:23, Santosh Shukla >> wrote: >> > On 29 D

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

mistakenly added wrong email-id of alex, looping his correct one. On 29 December 2015 at 21:23, Santosh Shukla wrote: > On 29 December 2015 at 18:58, Arnd Bergmann wrote: >> On Wednesday 23 December 2015 17:04:40 Santosh Shukla wrote: >>> On 23 December 2015 at 03:26, Ar

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

On 29 December 2015 at 18:58, Arnd Bergmann wrote: > On Wednesday 23 December 2015 17:04:40 Santosh Shukla wrote: >> On 23 December 2015 at 03:26, Arnd Bergmann wrote: >> > On Tuesday 22 December 2015, Santosh Shukla wrote: >> >> } >> >> >> >&g

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

On 29 December 2015 at 18:58, Arnd Bergmann <a...@arndb.de> wrote: > On Wednesday 23 December 2015 17:04:40 Santosh Shukla wrote: >> On 23 December 2015 at 03:26, Arnd Bergmann <a...@arndb.de> wrote: >> > On Tuesday 22 December 2015, Santosh Shukla wrote: >>

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

mistakenly added wrong email-id of alex, looping his correct one. On 29 December 2015 at 21:23, Santosh Shukla <santosh.shu...@linaro.org> wrote: > On 29 December 2015 at 18:58, Arnd Bergmann <a...@arndb.de> wrote: >> On Wednesday 23 December 2015 17:04:40 Santosh Shukla wrot

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

On Tue, Dec 29, 2015 at 9:50 PM, Arnd Bergmann <a...@arndb.de> wrote: > On Tuesday 29 December 2015 21:25:15 Santosh Shukla wrote: >> mistakenly added wrong email-id of alex, looping his correct one. >> >> On 29 December 2015 at 21:23, Santosh Shukla <santos

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

On 23 December 2015 at 03:26, Arnd Bergmann wrote: > On Tuesday 22 December 2015, Santosh Shukla wrote: >> } >> >> So I care for /dev/ioport types interface who could do more than byte >> data copy to/from user-space. I tested this patch with little >> modif

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

On 23 December 2015 at 03:26, Arnd Bergmann <a...@arndb.de> wrote: > On Tuesday 22 December 2015, Santosh Shukla wrote: >> } >> >> So I care for /dev/ioport types interface who could do more than byte >> data copy to/from user-space. I tested this patch with litt

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

On 30 May 2014 at 17:02, Arnd Bergmann wrote: > On Thursday 29 May 2014 06:38:35 H. Peter Anvin wrote: >> On 05/29/2014 02:26 AM, Arnd Bergmann wrote: >> > On Wednesday 28 May 2014 14:41:52 H. Peter Anvin wrote: >> >> On 05/19/2014 05:36 AM, Arnd Bergmann wrote: >> >>> >> >>> My feeling is that

Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports

On 30 May 2014 at 17:02, Arnd Bergmann wrote: > On Thursday 29 May 2014 06:38:35 H. Peter Anvin wrote: >> On 05/29/2014 02:26 AM, Arnd Bergmann wrote: >> > On Wednesday 28 May 2014 14:41:52 H. Peter Anvin wrote: >> >> On 05/19/2014 05:36 AM, Arnd Bergmann wrote: >> >>> >> >>> My

Re: [Query] Spurious interrupts from clockevent device on X86 Ivybridge

On 11 December 2014 at 10:14, Preeti U Murthy wrote: > On 12/10/2014 06:22 PM, Viresh Kumar wrote: >> On 10 December 2014 at 18:03, Preeti U Murthy >> wrote: >> >>> Right. We get an interrupt when nobody had asked for it to be delivered >>> or had asked for it to be delivered and later canceled

Re: [Query] Spurious interrupts from clockevent device on X86 Ivybridge

On 11 December 2014 at 10:14, Preeti U Murthy pre...@linux.vnet.ibm.com wrote: On 12/10/2014 06:22 PM, Viresh Kumar wrote: On 10 December 2014 at 18:03, Preeti U Murthy pre...@linux.vnet.ibm.com wrote: Right. We get an interrupt when nobody had asked for it to be delivered or had asked for

[Query] Spurious interrupts from clockevent device on X86 Ivybridge

Hi Guys, I have been chasing spurious clockevent interrupts (In HIGHRES mode) on my x86 IvyBridge server and stuck on some blockers (mostly due to lack of knowledge) and need some help.. What does spurious mean ? I take it as the case when a core is unnecessarily interrupted by the clockevent

[Query] Spurious interrupts from clockevent device on X86 Ivybridge

Hi Guys, I have been chasing spurious clockevent interrupts (In HIGHRES mode) on my x86 IvyBridge server and stuck on some blockers (mostly due to lack of knowledge) and need some help.. What does spurious mean ? I take it as the case when a core is unnecessarily interrupted by the clockevent