From: Guenter Roeck <guenter.roeck@ericsson.com>
To: linux-mips@linux-mips.org
Subject: VMALLOC_END, TASK_SIZE and FIXADDR_START for 64 bit MIPS kernels
Date: Wed, 3 Feb 2010 14:22:50 -0800 [thread overview]
Message-ID: <20100203222250.GA21139@ericsson.com> (raw)
Hi,
since it came up during the review of the patch for virtual memory detection
on 64 bit mips kernels, I looked further into making vmalloc_end
a variable and TASK_SIZE dependent on the virtual memory size.
That turned out to be relatively straightforward, and I have a working patch.
The one question I still have is about FIXADDR_START. It is currently
set to one of 0xff000000, 0xfffe0000, or (0xff000000 - 0x20000),
depending on the target CPU.
Quoting from one of the comments during the review,
" ... ensure the value of vmalloc_end is <= FIXADDR_START".
Obviously that is currently not the case. Is that a concern, or is it good as it is ?
Thanks,
Guenter
next reply other threads:[~2010-02-03 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 22:22 Guenter Roeck [this message]
2010-02-08 14:02 ` VMALLOC_END, TASK_SIZE and FIXADDR_START for 64 bit MIPS kernels Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100203222250.GA21139@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox