On 06-05-08 05:15, Peter Teoh wrote:
Greg: added to the CC as one of the LDD3 authors. perhaps it's interesting
to note for a possible followup edition.
Please be aware that /proc/iomem lists physical addresses, while his
request was for availability of a virtual address.
I was aware of
Hi..
On Sun, May 4, 2008 at 6:48 PM, Rene Herman [EMAIL PROTECTED] wrote:
It depends. There's obviously no way that the user stack can reside in
kernelspace (well, sanely) so the question is, is there any way to have
kernelspace limited to the last 512M instead of the last 1G as usual.
On 05-05-08 11:38, Mulyadi Santosa wrote:
On Sun, May 4, 2008 at 6:48 PM, Rene Herman [EMAIL PROTECTED] wrote:
It depends. There's obviously no way that the user stack can reside in
kernelspace (well, sanely) so the question is, is there any way to have
kernelspace limited to the last 512M
On Sun, May 4, 2008 at 6:35 PM, Anant Narayanan [EMAIL PROTECTED] wrote:
Hi,
While implementing a binary format loader for a foreign executable format,
What foreign executable is that?
As far as I can see, Linux kernel can handle the following types of
foreign executable:
./fs/binfmt_elf.c:
Thank you for pointing out my mistakes.it helped to improve my
understanding..and I have learned something!!!
On Tue, May 6, 2008 at 1:53 AM, Rene Herman [EMAIL PROTECTED] wrote:
On 05-05-08 18:03, Peter Teoh wrote:
Specifically, if u cat /proc/iomem:
/proccat iomem
On Sun, May 4, 2008 at 7:48 PM, Rene Herman [EMAIL PROTECTED] wrote:
On 04-05-08 12:35, Anant Narayanan wrote:
While implementing a binary format loader for a foreign executable format,
we have found the need to setup the user stack starting at (virtual) address
0xE000 instead of the
Hi,
While implementing a binary format loader for a foreign executable
format, we have found the need to setup the user stack starting at
(virtual) address 0xE000 instead of the usual 0xC000. However
a call to setup_arg_pages() with that value returns -EINVAL.
Is there any way to
