> the ability to change the default CS and DS segments
> as well.
This does not make any sense.
The user is free to load any selector in %cs/%ds/%es/%ss so the default
flat segments should be left alone so that a process can have the flat
segments _plus_ all the tls entries.
> although i suspect Wine needs a 16-bit entry, while
> the APM one is a 32-bit entry ...
AFAIK this only matters for code and stack segments and anyway the APM
one should be a 16-bit entry since it exists because the BIOS wrongly
assumes that it is a real-mode segment.
Anyway, isn't it better to put the user segments in a cacheline that
doesn't already lose one entry to the null selector? (and leave the
first one either empty or for BIOS/boot selectors)
--=-VXMkk8DMjZ5RpQKX5yAv
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQA9V8bldjkty3ft5+cRAqU5AJ4xy0OvOrZjOjR6ypkXQO3t0lbWuwCgrXRg
OTuObXz1j9nOdLAXPAtBJq8=
=WntD
-----END PGP SIGNATURE-----
--=-VXMkk8DMjZ5RpQKX5yAv--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/