On 01/09/2012 09:21 AM, Alexander Graf wrote: > > On 21.12.2011, at 02:34, Scott Wood wrote: > >> Currently 32-bit only cares about this for choice of exception >> vector, which is done in core-specific code. However, KVM will >> want to distinguish as well. >> >> Signed-off-by: Scott Wood <scottw...@freescale.com> >> --- >> arch/powerpc/include/asm/cputable.h | 5 +++-- >> 1 files changed, 3 insertions(+), 2 deletions(-) >> >> diff --git a/arch/powerpc/include/asm/cputable.h >> b/arch/powerpc/include/asm/cputable.h >> index e30442c..033ad30 100644 >> --- a/arch/powerpc/include/asm/cputable.h >> +++ b/arch/powerpc/include/asm/cputable.h >> @@ -375,7 +375,8 @@ extern const char *powerpc_base_platform; >> #define CPU_FTRS_47X (CPU_FTRS_440x6) >> #define CPU_FTRS_E200 (CPU_FTR_USE_TB | CPU_FTR_SPE_COMP | \ >> CPU_FTR_NODSISRALIGN | CPU_FTR_COHERENT_ICACHE | \ >> - CPU_FTR_UNIFIED_ID_CACHE | CPU_FTR_NOEXECUTE) >> + CPU_FTR_UNIFIED_ID_CACHE | CPU_FTR_NOEXECUTE | \ >> + CPU_FTR_DEBUG_LVL_EXC) > > KVM on E200?
This isn't a KVM patch, it's a patch to make CPU_FTR_DEBUG_LVL_EXC be set properly on 32-bit chips. e200 has this CPU feature. -Scott _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
