From: Arun Sharma <arun.sharma@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] long format VHPT
Date: Fri, 26 Sep 2003 22:24:13 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106461515127683@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106453902218848@msgid-missing>
Darren Williams wrote:
> +#ifdef CONFIG_IA64_LONG_FORMAT_VHPT
> + int cpu = smp_processor_id();
> + int i;
> +
> + if (cpu = 0)
> + {
> + /* We allocate all VHPTs here as we may not have enough contiguous memory later */
> + /* Also, we cannot use __get_free_pages on the target processor (until after init_cpu) */
> + for (i = 0; i < NR_CPUS; i++){
> + vhpt_base[i] = (unsigned long)__alloc_bootmem(LONG_VHPT_SIZE, LONG_VHPT_SIZE, __pa(MAX_DMA_ADDRESS));
> + printk(KERN_INFO "CPU %d: Long format VHPT initialised at base address: 0x%lx\n", i, vhpt_base[i]);
> + }
> + }
> +#endif
- Can we avoid allocating VHPTs for non-existent CPUs ?
- How about calling alloc_bootmem on cpu0 and __get_free_pages on secondary cpus ?
- Does the VHPT size have to be a config option ? Can we not size it based on the size of the physical memory and some user supplied multiplier ?
I noticed that when we hit ia64_mmu_init() on a secondary processor, cpu0 has already made successful calls to __get_free_pages(). But calls from the secondary cpus fail. Does anyone know why ?
-Arun
PS: patches for some of the above available, but they're based on Matt's earlier patch and need cleaning up.
next prev parent reply other threads:[~2003-09-26 22:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 1:12 [PATCH] long format VHPT Darren Williams
2003-09-26 22:24 ` Arun Sharma [this message]
2003-09-26 23:42 ` Darren Williams
2003-09-28 23:44 ` Chen, Kenneth W
2003-09-29 17:43 ` Arun Sharma
2003-09-29 23:48 ` Darren Williams
2003-09-30 18:25 ` Arun Sharma
2003-10-01 0:58 ` Arun Sharma
2003-10-02 1:30 ` Arun Sharma
2003-10-02 1:51 ` Peter Chubb
2003-10-02 2:10 ` Matt Chapman
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=marc-linux-ia64-106461515127683@msgid-missing \
--to=arun.sharma@intel.com \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.