Re: [PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-04-06 Thread James Morse
Hi gengdongjiu, On 05/04/17 00:05, gengdongjiu wrote: > thanks for the patch, have you consider to told Qemu or KVM tools > the reason for this bus error(SEA/SEI)? They should never need to know. We should treat Qemu/kvmtool like any other program. Programs should only need to know about the

Re: [PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-04-04 Thread gengdongjiu
Hi James, thanks for the patch, have you consider to told Qemu or KVM tools the reason for this bus error(SEA/SEI)? when Qemu or KVM tools get this SIGBUS signal, it do not know receive this SIGBUS due to SEA or SEI. OR KVM only send this SIGBUS when encounter SEA? if so, for the SEI case, how

Re: [PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-03-28 Thread Christoffer Dall
On Tue, Mar 28, 2017 at 03:50:51PM +0100, Punit Agrawal wrote: > Christoffer Dall writes: > > > On Mon, Mar 27, 2017 at 02:31:44PM +0100, Punit Agrawal wrote: > >> Christoffer Dall writes: > >> > >> > On Mon, Mar 27, 2017 at 01:00:56PM +0100, James Morse

Re: [PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-03-28 Thread Punit Agrawal
Christoffer Dall writes: > On Mon, Mar 27, 2017 at 02:31:44PM +0100, Punit Agrawal wrote: >> Christoffer Dall writes: >> >> > On Mon, Mar 27, 2017 at 01:00:56PM +0100, James Morse wrote: >> >> Hi guys, >> >> >> >> On 27/03/17 12:20, Punit Agrawal wrote: >>

Re: [PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-03-27 Thread Christoffer Dall
On Mon, Mar 27, 2017 at 02:31:44PM +0100, Punit Agrawal wrote: > Christoffer Dall writes: > > > On Mon, Mar 27, 2017 at 01:00:56PM +0100, James Morse wrote: > >> Hi guys, > >> > >> On 27/03/17 12:20, Punit Agrawal wrote: > >> > Christoffer Dall writes: > >>

Re: [PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-03-27 Thread Punit Agrawal
Marc Zyngier writes: > On 27/03/17 14:31, Punit Agrawal wrote: >> Christoffer Dall writes: >> >>> On Mon, Mar 27, 2017 at 01:00:56PM +0100, James Morse wrote: Hi guys, On 27/03/17 12:20, Punit Agrawal wrote: > Christoffer Dall

Re: [PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-03-27 Thread Marc Zyngier
On 27/03/17 14:31, Punit Agrawal wrote: > Christoffer Dall writes: > >> On Mon, Mar 27, 2017 at 01:00:56PM +0100, James Morse wrote: >>> Hi guys, >>> >>> On 27/03/17 12:20, Punit Agrawal wrote: Christoffer Dall writes: > On Wed, Mar 15, 2017 at

Re: [PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-03-27 Thread Punit Agrawal
Christoffer Dall writes: > On Mon, Mar 27, 2017 at 01:00:56PM +0100, James Morse wrote: >> Hi guys, >> >> On 27/03/17 12:20, Punit Agrawal wrote: >> > Christoffer Dall writes: >> >> On Wed, Mar 15, 2017 at 04:07:27PM +, James Morse wrote: >> >>> Once we

Re: [PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-03-27 Thread Christoffer Dall
On Mon, Mar 27, 2017 at 01:00:56PM +0100, James Morse wrote: > Hi guys, > > On 27/03/17 12:20, Punit Agrawal wrote: > > Christoffer Dall writes: > >> On Wed, Mar 15, 2017 at 04:07:27PM +, James Morse wrote: > >>> Once we enable ARCH_SUPPORTS_MEMORY_FAILURE on arm64[0],

Re: [PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-03-27 Thread James Morse
Hi guys, On 27/03/17 12:20, Punit Agrawal wrote: > Christoffer Dall writes: >> On Wed, Mar 15, 2017 at 04:07:27PM +, James Morse wrote: >>> Once we enable ARCH_SUPPORTS_MEMORY_FAILURE on arm64[0], notifications for >>> broken memory can call memory_failure() in

Re: [PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-03-27 Thread Punit Agrawal
Christoffer Dall writes: > On Wed, Mar 15, 2017 at 04:07:27PM +, James Morse wrote: >> Once we enable ARCH_SUPPORTS_MEMORY_FAILURE on arm64[0], notifications for >> broken memory can call memory_failure() in mm/memory-failure.c to deliver >> SIGBUS to any user space process

Re: [PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-03-24 Thread Christoffer Dall
On Wed, Mar 15, 2017 at 04:07:27PM +, James Morse wrote: > Once we enable ARCH_SUPPORTS_MEMORY_FAILURE on arm64[0], notifications for > broken memory can call memory_failure() in mm/memory-failure.c to deliver > SIGBUS to any user space process using the page, and notify all the > in-kernel

Re: [PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-03-17 Thread Punit Agrawal
Hi James, One comment at the end. James Morse writes: > Once we enable ARCH_SUPPORTS_MEMORY_FAILURE on arm64[0], notifications for > broken memory can call memory_failure() in mm/memory-failure.c to deliver > SIGBUS to any user space process using the page, and notify all

[PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory

2017-03-15 Thread James Morse
Once we enable ARCH_SUPPORTS_MEMORY_FAILURE on arm64[0], notifications for broken memory can call memory_failure() in mm/memory-failure.c to deliver SIGBUS to any user space process using the page, and notify all the in-kernel users. If the page corresponded with guest memory, KVM will unmap this