Searched hist:ad0a048b (Results 1 – 4 of 4) sorted by relevance
/openbmc/linux/arch/powerpc/kvm/ |
H A D | book3s.c | ad0a048b Wed Mar 24 15:48:30 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Add OSI hypercall interface
MOL uses its own hypercall interface to call back into userspace when the guest wants to do something.
So let's implement that as an exit reason, specify it with a CAP and only really use it when userspace wants us to.
The only user of it so far is MOL.
Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Avi Kivity <avi@redhat.com> ad0a048b Wed Mar 24 15:48:30 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Add OSI hypercall interface MOL uses its own hypercall interface to call back into userspace when the guest wants to do something. So let's implement that as an exit reason, specify it with a CAP and only really use it when userspace wants us to. The only user of it so far is MOL. Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Avi Kivity <avi@redhat.com>
|
H A D | powerpc.c | ad0a048b Wed Mar 24 15:48:30 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Add OSI hypercall interface
MOL uses its own hypercall interface to call back into userspace when the guest wants to do something.
So let's implement that as an exit reason, specify it with a CAP and only really use it when userspace wants us to.
The only user of it so far is MOL.
Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Avi Kivity <avi@redhat.com> ad0a048b Wed Mar 24 15:48:30 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Add OSI hypercall interface MOL uses its own hypercall interface to call back into userspace when the guest wants to do something. So let's implement that as an exit reason, specify it with a CAP and only really use it when userspace wants us to. The only user of it so far is MOL. Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Avi Kivity <avi@redhat.com>
|
/openbmc/linux/arch/powerpc/include/asm/ |
H A D | kvm_book3s.h | ad0a048b Wed Mar 24 15:48:30 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Add OSI hypercall interface
MOL uses its own hypercall interface to call back into userspace when the guest wants to do something.
So let's implement that as an exit reason, specify it with a CAP and only really use it when userspace wants us to.
The only user of it so far is MOL.
Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Avi Kivity <avi@redhat.com> ad0a048b Wed Mar 24 15:48:30 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Add OSI hypercall interface MOL uses its own hypercall interface to call back into userspace when the guest wants to do something. So let's implement that as an exit reason, specify it with a CAP and only really use it when userspace wants us to. The only user of it so far is MOL. Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Avi Kivity <avi@redhat.com>
|
H A D | kvm_host.h | ad0a048b Wed Mar 24 15:48:30 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Add OSI hypercall interface
MOL uses its own hypercall interface to call back into userspace when the guest wants to do something.
So let's implement that as an exit reason, specify it with a CAP and only really use it when userspace wants us to.
The only user of it so far is MOL.
Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Avi Kivity <avi@redhat.com> ad0a048b Wed Mar 24 15:48:30 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Add OSI hypercall interface MOL uses its own hypercall interface to call back into userspace when the guest wants to do something. So let's implement that as an exit reason, specify it with a CAP and only really use it when userspace wants us to. The only user of it so far is MOL. Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Avi Kivity <avi@redhat.com>
|