Home
last modified time | relevance | path

Searched hist:"5 c6cedf488a1144ac4f683f3ea1a642533d1dcd2" (Results 1 – 3 of 3) sorted by relevance

/openbmc/linux/arch/powerpc/include/asm/
H A Dkvm_para.hdiff 5c6cedf488a1144ac4f683f3ea1a642533d1dcd2 Thu Jul 29 07:47:49 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Add PV guest critical sections

When running in hooked code we need a way to disable interrupts without
clobbering any interrupts or exiting out to the hypervisor.

To achieve this, we have an additional critical field in the shared page. If
that field is equal to the r1 register of the guest, it tells the hypervisor
that we're in such a critical section and thus may not receive any interrupts.

Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Avi Kivity <avi@redhat.com>
/openbmc/linux/arch/powerpc/kvm/
H A Dbook3s.cdiff 5c6cedf488a1144ac4f683f3ea1a642533d1dcd2 Thu Jul 29 07:47:49 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Add PV guest critical sections

When running in hooked code we need a way to disable interrupts without
clobbering any interrupts or exiting out to the hypervisor.

To achieve this, we have an additional critical field in the shared page. If
that field is equal to the r1 register of the guest, it tells the hypervisor
that we're in such a critical section and thus may not receive any interrupts.

Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Avi Kivity <avi@redhat.com>
H A Dbooke.cdiff 5c6cedf488a1144ac4f683f3ea1a642533d1dcd2 Thu Jul 29 07:47:49 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Add PV guest critical sections

When running in hooked code we need a way to disable interrupts without
clobbering any interrupts or exiting out to the hypervisor.

To achieve this, we have an additional critical field in the shared page. If
that field is equal to the r1 register of the guest, it tells the hypervisor
that we're in such a critical section and thus may not receive any interrupts.

Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Avi Kivity <avi@redhat.com>