Re: i486 emu in mainline?

Pavel Machek
2004-05-31T13:35:23Z

Hi!

> >> It was intentional for speed purpose. The areas are checked once with
> >> verify_area() when we need to access memory, then data is copied directly
> >> from/to memory. I don't think there's any risk, but I can be wrong.
> >
> > Which will break with 4G/4G. You must use at least __get_user().
>
> A 386 with a 4G/4G split, I'd like to see that.

I believe you could...

1) some 586 class machines do not know 486 opcodes

2) this is for rescue kernel. If you want to be able to rescue 64GB machine *and* rescue 486 too,
this+4G/4G is right choice ;-)

--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms