Re: [PATCH v2 3/10] KVM: MMU: fix direct sp's access corruptted
From: Xiao Guangrong
Date: Mon Jun 28 2010 - 21:21:15 EST
Avi Kivity wrote:
> On 06/28/2010 01:02 PM, Xiao Guangrong wrote:
>> Avi Kivity wrote:
>>> Instead of adding a new bit, can you encode the protection in the direct
>>> sp's access bits? So we'll have one sp for read-only or
>>> writeable-but-not-dirty small pages, and another sp for
>>> writeable-and-dirty small pages.
>> It looks like it can't solve all problems, it fix the access corrupted,
>> but will cause D bit losed:
>> mapping A and mapping B both are writable-and-dirty, when mapping A write
>> #PF occurs, the mapping is writable, then we can't set B's D bit anymore.
> If B is writeable-and-dirty, then it's D bit is already set, and we
> don't need to do anything.
> If B is writeable-and-clean, then we'll have an spte pointing to a
> read-only sp, so we'll get a write fault on access and an opportunity to
> set the D bit.
Sorry, a typo in my reply, i mean mapping A and B both are writable-and-clean,
while A occurs write-#PF, we should change A's spte map to writable sp, if we
only update the spte in writable-and-clean sp(form readonly to writable), the B's
D bit will miss set.
>> Anyway, i think we should re-intall the mapping when the state is
>> changed. :-(
> When the gpte is changed from read-only to writeable or from clean to
> dirty, we need to update the spte, yes. But that's true for other sptes
> as well, not just large gptes.
I think the indirect sp is not hurt by this bug since for the indirect sp, the access
just form its upper-level, and the D bit is only in the last level, when we change the
pte's access, is not affect its sp's access.
But for direct sp, the sp's access is form all level. and different mapping that not share
the last mapping page will have the same last sp.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/