Searched hist:"8 b6db3bc965c204db6868d4005808b4fdc9c46d7" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/arch/powerpc/kvm/ |
| H A D | book3s_32_mmu_host.c | diff 8b6db3bc965c204db6868d4005808b4fdc9c46d7 Sun Aug 15 01:04:24 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Implement correct SID mapping on Book3s_32
Up until now we were doing segment mappings wrong on Book3s_32. For Book3s_64
we were using a trick where we know that a single mmu_context gives us 16 bits
of context ids.
The mm system on Book3s_32 instead uses a clever algorithm to distribute VSIDs
across the available range, so a context id really only gives us 16 available
VSIDs.
To keep at least a few guest processes in the SID shadow, let's map a number of
contexts that we can use as VSID pool. This makes the code be actually correct
and shouldn't hurt performance too much.
Signed-off-by: Alexander Graf <agraf@suse.de>
|
| H A D | book3s_64_mmu_host.c | diff 8b6db3bc965c204db6868d4005808b4fdc9c46d7 Sun Aug 15 01:04:24 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Implement correct SID mapping on Book3s_32
Up until now we were doing segment mappings wrong on Book3s_32. For Book3s_64
we were using a trick where we know that a single mmu_context gives us 16 bits
of context ids.
The mm system on Book3s_32 instead uses a clever algorithm to distribute VSIDs
across the available range, so a context id really only gives us 16 available
VSIDs.
To keep at least a few guest processes in the SID shadow, let's map a number of
contexts that we can use as VSID pool. This makes the code be actually correct
and shouldn't hurt performance too much.
Signed-off-by: Alexander Graf <agraf@suse.de>
|
| /openbmc/linux/arch/powerpc/include/asm/ |
| H A D | kvm_book3s.h | diff 8b6db3bc965c204db6868d4005808b4fdc9c46d7 Sun Aug 15 01:04:24 CDT 2010 Alexander Graf <agraf@suse.de> KVM: PPC: Implement correct SID mapping on Book3s_32
Up until now we were doing segment mappings wrong on Book3s_32. For Book3s_64
we were using a trick where we know that a single mmu_context gives us 16 bits
of context ids.
The mm system on Book3s_32 instead uses a clever algorithm to distribute VSIDs
across the available range, so a context id really only gives us 16 available
VSIDs.
To keep at least a few guest processes in the SID shadow, let's map a number of
contexts that we can use as VSID pool. This makes the code be actually correct
and shouldn't hurt performance too much.
Signed-off-by: Alexander Graf <agraf@suse.de>
|