|
|
Log in / Subscribe / Register

3.16 merge window, part 2

3.16 merge window, part 2

Posted Jun 27, 2014 16:27 UTC (Fri) by khim (subscriber, #9252)
In reply to: 3.16 merge window, part 2 by eru
Parent article: 3.16 merge window, part 2

What have you tried to find in Google? Request How to modify LDT in Linux returns the appropriate manpage as the first hit!


to post comments

3.16 merge window, part 2

Posted Jun 28, 2014 10:12 UTC (Sat) by eru (subscriber, #2753) [Link] (2 responses)

Thanks, khim. I guess I was too dense to include "ldt" in my queries. The manpage is not too informative, though. It does not say if I can extend the LDT with the call, and a quick test on my home x86_64 machine just returned 0 as the size, when reading the LDT (maybe this works only in 32-bit processes?). I would like to be able to allocate at least about ten LDT entries, in order to partially simulate a legacy system, where code, data and stack are all in different segments, and memory allocation calls return fresh segments with their own LDT entries.

Oh well, I probably have to read relevant bit of the kernel source for further investigations.

3.16 merge window, part 2

Posted Jun 28, 2014 12:43 UTC (Sat) by khim (subscriber, #9252) [Link] (1 responses)

LDT is unusable in 64bit mode, yes. This is hardware limitation. It's fully usable in 32bit process even on x86-64 system with 64bit kernel. For 32bit process there are examples (e.g. you could look on NaCl here).

3.16 merge window, part 2

Posted Jun 29, 2014 12:11 UTC (Sun) by eru (subscriber, #2753) [Link]

Thanks again, I will study that sample.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds