diff options
author | Bharat Bhushan <r65777@freescale.com> | 2013-11-15 11:01:13 +0530 |
---|---|---|
committer | Alexander Graf <agraf@suse.de> | 2014-01-09 10:15:04 +0100 |
commit | 30a91fe24b7a6475d22d22fb0f772318ed435a1d (patch) | |
tree | 0c01cb9668342e5ce0bd15ff3e34e353a922bb92 /arch/powerpc/kernel/eeh_dev.c | |
parent | 595e4f7e697e2e6fb252f6be6a83d5b9460b59a3 (diff) |
kvm: booke: clear host tlb reference flag on guest tlb invalidation
On booke, "struct tlbe_ref" contains host tlb mapping information
(pfn: for guest-pfn to pfn, flags: attribute associated with this mapping)
for a guest tlb entry. So when a guest creates a TLB entry then
"struct tlbe_ref" is set to point to valid "pfn" and set attributes in
"flags" field of the above said structure. When a guest TLB entry is
invalidated then flags field of corresponding "struct tlbe_ref" is
updated to point that this is no more valid, also we selectively clear
some other attribute bits, example: if E500_TLB_BITMAP was set then we clear
E500_TLB_BITMAP, if E500_TLB_TLB0 is set then we clear this.
Ideally we should clear complete "flags" as this entry is invalid and does not
have anything to re-used. The other part of the problem is that when we use
the same entry again then also we do not clear (started doing or-ing etc).
So far it was working because the selectively clearing mentioned above
actually clears "flags" what was set during TLB mapping. But the problem
starts coming when we add more attributes to this then we need to selectively
clear them and which is not needed.
Signed-off-by: Bharat Bhushan <bharat.bhushan@freescale.com>
Reviewed-by: Scott Wood <scottwood@freescale.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'arch/powerpc/kernel/eeh_dev.c')
0 files changed, 0 insertions, 0 deletions