Hi guys,
As you know kvmppc uses shadow_ref to record connections between gtlbes and pages.
44x implement it as kvmppc_44x_shadow_ref, and e500 implement it as kvmppc_e500_shadow_ref in recent patches.
The problem for e500 now is that, the shadow_ref for TLB0 doesn't reflect the hardware situation
but has one-one mappings to guest TLB0 entries.
This doesn't sounds logic, and make me hard to try new things, such as redirect guest TLB1 to host TLB0, large guest TLB,
44x is fine for kvmppc_44x_shadow_ref reflects the hardware.
So I'm thinking about seperating kvmppc_e500_shadow_ref from guest TLB0 and connect it with hardware.
Then I notice both 44x and e500 implement shadow_ref as per-vcpu data.
Can shadow_ref be per-core data?
This looks like could save some memory.
I don't want to do the wrong thing at the first step, so any suggestion?
��.n��������+%������w��{.n�����o��^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�m
