From: monstr@monstr.eu (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: arm cortex a9, smp bootup requirement
Date: Fri, 06 Jul 2012 11:08:29 +0200 [thread overview]
Message-ID: <4FF6AB0D.8010105@monstr.eu> (raw)
Hi,
can someone correct me about smp boot requirement for Linux?
We are fixing ARM zynq smp bootup code and would like to be sure
that out bootup code is correct.
I have found some requirements from standalone boot up code
which is invalidate dcache, icache, branch predictor array
and flush TLB.
I have found in secondary_start_kernel that TLB are flushed
by local_flush_tlb_all function.
But haven't found any cache invalidation calling.
I think it is required and we could be added to platform_secondary_init.
Or is it requirement which has to be fulfil by bootloader before
secondary_startup is called?
We have the option to reset specific cpu in the system and cpu
starts from 0x0 with cache off and in non-virtual mode
where we place simple jump trampoline to the secondary_startup
function. If cache invalidation is required by Linux we can extend this code
to do it.
Jumping trampoline is:
0x0: ldr r0, [8]
0x4: mov pc, r0
0x8: jump address
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
WARNING: multiple messages have this Message-ID (diff)
From: Michal Simek <monstr@monstr.eu>
To: LKML <linux-kernel@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
Russell King <linux@arm.linux.org.uk>
Cc: John Linn <linnj@xilinx.com>,
John Williams <john.williams@petalogix.com>
Subject: arm cortex a9, smp bootup requirement
Date: Fri, 06 Jul 2012 11:08:29 +0200 [thread overview]
Message-ID: <4FF6AB0D.8010105@monstr.eu> (raw)
Hi,
can someone correct me about smp boot requirement for Linux?
We are fixing ARM zynq smp bootup code and would like to be sure
that out bootup code is correct.
I have found some requirements from standalone boot up code
which is invalidate dcache, icache, branch predictor array
and flush TLB.
I have found in secondary_start_kernel that TLB are flushed
by local_flush_tlb_all function.
But haven't found any cache invalidation calling.
I think it is required and we could be added to platform_secondary_init.
Or is it requirement which has to be fulfil by bootloader before
secondary_startup is called?
We have the option to reset specific cpu in the system and cpu
starts from 0x0 with cache off and in non-virtual mode
where we place simple jump trampoline to the secondary_startup
function. If cache invalidation is required by Linux we can extend this code
to do it.
Jumping trampoline is:
0x0: ldr r0, [8]
0x4: mov pc, r0
0x8: jump address
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next reply other threads:[~2012-07-06 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 9:08 Michal Simek [this message]
2012-07-06 9:08 ` arm cortex a9, smp bootup requirement Michal Simek
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=4FF6AB0D.8010105@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-arm-kernel@lists.infradead.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.