Re: [RFC PATCH v1 2/4] KVM: arm64: GICv4.1: Try to save hw pending state in save_pending_tables

2020-11-24 Thread Shenming Lu
On 2020/11/24 16:26, Marc Zyngier wrote: > On 2020-11-24 07:40, Shenming Lu wrote: >> On 2020/11/23 17:18, Marc Zyngier wrote: >>> On 2020-11-23 06:54, Shenming Lu wrote: After pausing all vCPUs and devices capable of interrupting, in order >>>     ^ >>> See my comment belo

Re: [RFC PATCH v1 2/4] KVM: arm64: GICv4.1: Try to save hw pending state in save_pending_tables

2020-11-24 Thread Marc Zyngier
On 2020-11-24 07:40, Shenming Lu wrote: On 2020/11/23 17:18, Marc Zyngier wrote: On 2020-11-23 06:54, Shenming Lu wrote: After pausing all vCPUs and devices capable of interrupting, in order     ^ See my comment below about this. to save the information of all interrupts,

Re: [RFC PATCH v1 2/4] KVM: arm64: GICv4.1: Try to save hw pending state in save_pending_tables

2020-11-23 Thread Shenming Lu
On 2020/11/23 17:18, Marc Zyngier wrote: > On 2020-11-23 06:54, Shenming Lu wrote: >> After pausing all vCPUs and devices capable of interrupting, in order >     ^ > See my comment below about this. > >> to save the information of all interrupts, besides flushing the pending >>

Re: [RFC PATCH v1 2/4] KVM: arm64: GICv4.1: Try to save hw pending state in save_pending_tables

2020-11-23 Thread Marc Zyngier
On 2020-11-23 06:54, Shenming Lu wrote: After pausing all vCPUs and devices capable of interrupting, in order ^ See my comment below about this. to save the information of all interrupts, besides flushing the pending states in kvm’s vgic, we also try to flush the states

[RFC PATCH v1 2/4] KVM: arm64: GICv4.1: Try to save hw pending state in save_pending_tables

2020-11-22 Thread Shenming Lu
After pausing all vCPUs and devices capable of interrupting, in order to save the information of all interrupts, besides flushing the pending states in kvm’s vgic, we also try to flush the states of VLPIs in the virtual pending tables into guest RAM, but we need to have GICv4.1 and safely unmap the