Re: [PATCH v22 7/9] ACPI: Record Generic Error Status Block(GESB) table

2020-02-02 Thread Igor Mammedov
On Sun, 2 Feb 2020 21:42:23 +0800 gengdongjiu wrote: > On 2020/1/28 23:29, Igor Mammedov wrote: > > On Wed, 8 Jan 2020 19:32:21 +0800 > > Dongjiu Geng wrote: > > > >> kvm_arch_on_sigbus_vcpu() error injection uses source_id as > >> index in etc/hardware_errors to find out Error Status Data >

Re: [PATCH v22 7/9] ACPI: Record Generic Error Status Block(GESB) table

2020-02-02 Thread gengdongjiu
On 2020/1/28 23:29, Igor Mammedov wrote: > On Wed, 8 Jan 2020 19:32:21 +0800 > Dongjiu Geng wrote: > >> kvm_arch_on_sigbus_vcpu() error injection uses source_id as >> index in etc/hardware_errors to find out Error Status Data >> Block entry corresponding to error source. So supported source_id >>

Re: [PATCH v22 7/9] ACPI: Record Generic Error Status Block(GESB) table

2020-01-28 Thread Igor Mammedov
On Wed, 8 Jan 2020 19:32:21 +0800 Dongjiu Geng wrote: > kvm_arch_on_sigbus_vcpu() error injection uses source_id as > index in etc/hardware_errors to find out Error Status Data > Block entry corresponding to error source. So supported source_id > values should be assigned here and not be changed

[PATCH v22 7/9] ACPI: Record Generic Error Status Block(GESB) table

2020-01-08 Thread Dongjiu Geng
kvm_arch_on_sigbus_vcpu() error injection uses source_id as index in etc/hardware_errors to find out Error Status Data Block entry corresponding to error source. So supported source_id values should be assigned here and not be changed afterwards to make sure that guest will write error into expecte