On Mon, 22 Feb 2016, Igor R wrote:
> What should happen if I map KSEG2 directly as a continuation of KSEG1,
> i.e. substitute TLB lookup with "address - (int32_t)KSEG1_BASE"? Guest
> Linux seems to work correctly (but maybe it's just a matter of luck?).
The 32-bit MIPS port of Linux uses KSEG2 f
> > Here is an excerpt from r4k_map_address(), related to addresses >=
0x8000.
> > Actually, it maps 0x8010 and 0xA010 to the same physical
> > address. What's the idea behind that?
>
> 0x8010 is kseg0 whereas 0xA010 is kseg1, both segments are
> unmapped thus both refer to the
> > Here is an excerpt from r4k_map_address(), related to addresses >=
0x8000.
> > Actually, it maps 0x8010 and 0xA010 to the same physical
> > address. What's the idea behind that?
>
> 0x8010 is kseg0 whereas 0xA010 is kseg1, both segments are
> unmapped thus both refer to the
On 22/02/16 06:56, Igor R wrote:
> Here is an excerpt from r4k_map_address(), related to addresses >= 0x8000.
> Actually, it maps 0x8010 and 0xA010 to the same physical
> address. What's the idea behind that?
0x8010 is kseg0 whereas 0xA010 is kseg1, both segments are
unmapped t
I have some issues when accessing guest Linux kernel memory above
0xC000 by means of cpu_memory_rw_debug (x86_64 host, MIPS guest),
and I'm trying to debug it.
Here is an excerpt from r4k_map_address(), related to addresses >= 0x8000.
Actually, it maps 0x8010 and 0xA010 to the same
