| /openbmc/linux/arch/powerpc/kvm/ |
| H A D | emulate.c | diff 9dd921cfea734409a931ccc6eafd7f09850311e9 Wed Nov 05 09:36:14 CST 2008 Hollis Blanchard <hollisb@us.ibm.com> KVM: ppc: Refactor powerpc.c to relocate 440-specific code
This introduces a set of core-provided hooks. For 440, some of these are
implemented by booke.c, with the rest in (the new) 44x.c.
Note that these hooks are link-time, not run-time. Since it is not possible to
build a single kernel for both e500 and 440 (for example), using function
pointers would only add overhead.
Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | Makefile | diff 9dd921cfea734409a931ccc6eafd7f09850311e9 Wed Nov 05 09:36:14 CST 2008 Hollis Blanchard <hollisb@us.ibm.com> KVM: ppc: Refactor powerpc.c to relocate 440-specific code
This introduces a set of core-provided hooks. For 440, some of these are
implemented by booke.c, with the rest in (the new) 44x.c.
Note that these hooks are link-time, not run-time. Since it is not possible to
build a single kernel for both e500 and 440 (for example), using function
pointers would only add overhead.
Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | Kconfig | diff 9dd921cfea734409a931ccc6eafd7f09850311e9 Wed Nov 05 09:36:14 CST 2008 Hollis Blanchard <hollisb@us.ibm.com> KVM: ppc: Refactor powerpc.c to relocate 440-specific code
This introduces a set of core-provided hooks. For 440, some of these are
implemented by booke.c, with the rest in (the new) 44x.c.
Note that these hooks are link-time, not run-time. Since it is not possible to
build a single kernel for both e500 and 440 (for example), using function
pointers would only add overhead.
Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | booke.c | diff 9dd921cfea734409a931ccc6eafd7f09850311e9 Wed Nov 05 09:36:14 CST 2008 Hollis Blanchard <hollisb@us.ibm.com> KVM: ppc: Refactor powerpc.c to relocate 440-specific code
This introduces a set of core-provided hooks. For 440, some of these are
implemented by booke.c, with the rest in (the new) 44x.c.
Note that these hooks are link-time, not run-time. Since it is not possible to
build a single kernel for both e500 and 440 (for example), using function
pointers would only add overhead.
Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | powerpc.c | diff 9dd921cfea734409a931ccc6eafd7f09850311e9 Wed Nov 05 09:36:14 CST 2008 Hollis Blanchard <hollisb@us.ibm.com> KVM: ppc: Refactor powerpc.c to relocate 440-specific code
This introduces a set of core-provided hooks. For 440, some of these are
implemented by booke.c, with the rest in (the new) 44x.c.
Note that these hooks are link-time, not run-time. Since it is not possible to
build a single kernel for both e500 and 440 (for example), using function
pointers would only add overhead.
Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| /openbmc/linux/arch/powerpc/include/asm/ |
| H A D | kvm_ppc.h | diff 9dd921cfea734409a931ccc6eafd7f09850311e9 Wed Nov 05 09:36:14 CST 2008 Hollis Blanchard <hollisb@us.ibm.com> KVM: ppc: Refactor powerpc.c to relocate 440-specific code
This introduces a set of core-provided hooks. For 440, some of these are
implemented by booke.c, with the rest in (the new) 44x.c.
Note that these hooks are link-time, not run-time. Since it is not possible to
build a single kernel for both e500 and 440 (for example), using function
pointers would only add overhead.
Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
|
| H A D | kvm_host.h | diff 9dd921cfea734409a931ccc6eafd7f09850311e9 Wed Nov 05 09:36:14 CST 2008 Hollis Blanchard <hollisb@us.ibm.com> KVM: ppc: Refactor powerpc.c to relocate 440-specific code
This introduces a set of core-provided hooks. For 440, some of these are
implemented by booke.c, with the rest in (the new) 44x.c.
Note that these hooks are link-time, not run-time. Since it is not possible to
build a single kernel for both e500 and 440 (for example), using function
pointers would only add overhead.
Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
|