Current guests don't do this, and it's not clear what we should do if they
try to turn on ECC or set various RAM latencies. When someone does this,
we'll have a better idea of what we should do about it.
Signed-off-by: Rusty Russell <rusty.russell@xxxxxxxxxx>
diff --git a/arch/arm/kvm/emulate.c b/arch/arm/kvm/emulate.c
index c07eb2b..b83e4ba 100644
--- a/arch/arm/kvm/emulate.c
+++ b/arch/arm/kvm/emulate.c
@@ -290,13 +290,10 @@ static const struct coproc_emulate coproc_emulate[] = {
{ CRn( 0), CRm( 1), Op1( 0), Op2( 2), is32, READ, read_id_dfr0},
/*
- * L2CTLR access:
- *
- * Ignore writes completely.
+ * L2CTLR access (guest wants to know #CPUs).
*
* FIXME: Hack Alert: Read zero as default case.
*/
- { CRn( 9), CRm( 0), Op1( 1), Op2( 2), is32, WRITE, ignore_write},
{ CRn( 9), CRm( 0), Op1( 1), Op2( 2), is32, READ, read_l2ctlr},
{ CRn( 9), CRm(DF), Op1(DF), Op2(DF), is32, WRITE, ignore_write},
{ CRn( 9), CRm(DF), Op1(DF), Op2(DF), is32, READ, read_zero},
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
