From: Sukanto Ghosh <sghosh(a)apm.com>
The format of the lower 32-bits of the 64-bit operand to 'dc cisw' is
unchanged from ARMv7 architecture and the upper bits are RES0. This
implies that the 'way' field of the operand of 'dc cisw' occupies the
bit-positions [31 .. (32-A)]. Due to the use of 64-bit extended operands
to 'clz', the existing implementation of __flush_dcache_all is incorrectly
placing the 'way' field in the bit-positions [63 .. (64-A)].
Signed-off-by: Sukanto Ghosh <sghosh(a)apm.com>
Tested-by: Anup Patel <anup.patel(a)linaro.org>
---
arch/arm64/mm/cache.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/mm/cache.S b/arch/arm64/mm/cache.S
index abe69b8..48a3860 100644
--- a/arch/arm64/mm/cache.S
+++ b/arch/arm64/mm/cache.S
@@ -52,7 +52,7 @@ loop1:
add x2, x2, #4 // add 4 (line length offset)
mov x4, #0x3ff
and x4, x4, x1, lsr #3 // find maximum number on the way size
- clz x5, x4 // find bit position of way size increment
+ clz w5, w4 // find bit position of way size increment
mov x7, #0x7fff
and x7, x7, x1, lsr #13 // extract max number of the index size
loop2:
--
1.7.9.5
=== David Long ===
=== Highlights ===
* Tixy voiced doubts about the approach I used for uprobes being
upstreamable due to some redundancy in the kprobe/uprobe code. We
talked about an alternative design which I now have partially implemented.
* Helped relocate the Nashua office to its new space.
=== Plans ===
* Continue with uprobe/kprobe
* Start building systemtap
=== Issues ===
* None
-dl
hi Nico & all,
After we studied the IKS code, we believe the code is general and
smoothly and can almost meet well for our own SoC's requirement; here
also have some questions want to confirm with you guys:
1. When outbound core wake up inbound core, the outbound core's thread
will sleep until the inbound core use MCPM’s early pork to send IPI;
a) Looks like this method somehow is due to TC2 board has long letancy
to power on/off cluster and core; right? How about to use polling
method? because on our own SoC, the wakenup interval will take _only_
about 10 ~ 20us;
b) The inbound core will send IPI to outbound core for the
synchronization, but at this point the inbound core's GIC's cpu
interface is disabled; so even the core's cpu interface is disabled, can
the core send SGI to other cores?
c) MCPM's patchset merged for mainline have no related function for
early pork, so later will early pork related functions be committed to
mainline?
2. Now the switching is an async operation, means after the function
bL_switch_request is return back, we cannot say switching has been
completed; so we have some concern for it.
For example, when switch from A15 core to A7 core, then maybe we want to
decrease the voltage so that can save power; if the switching is an
async operation, then it maybe introduce the issue is: after return back
from the function bL_switch_request, then s/w will decrease the voltage;
but at the meantime, the real switching is ongoing on another pair cores.
i browser the git log and get to know at the beginning the switching is
synced by using kernel's workqueue, later changed to use a dedicated
kernel thread with FIFO type; do u think it's better to go ahead to add
sync method for switching?
3. After enabled switcher, then it will disable hotplug.
Actually current code can support hotplug with IKS; because with IKS,
the logical core will map the according physical core id and GIC's
interface id, so that it can make sure if the system has hotplugged out
which physical core, later the kernel can hotplug in this physical core.
So could u give more hints why iks need disable hotplug?
--
Thx,
Leo Yan
=== Highlights ===
* Did a first pass at addressing remapping issue for volatile ranges
(still waiting on Minchan's feedback)
* Updated Anton's KDB/FIQ patch queues. Pinged Jason and sent the short
list out to lkml for feedback.
* Cherry-picked the ION code into a dev tree against 3.10 to learn more
about it in prep for future discussions.
* Reached out to Arnd on ION dma questions.
* Updated linaro.android tree to pre-3.10-rc1, ran into some trouble
testing since panda wasn't booting, but Tixy helped with testing and
Kevin followed up with a solution for panda.
* Sent out some requests-for-participation emails for Linux Plumbers
Android miniconf
* Talked w/ Deepak about drivers/clocksource issues and other planning
* Reviewed YongQins's get_user macro fix
* Reviewed blueprints and had bi-weekly hangout with android upstreaming
team
* Reviewed Dmitry's vfat ioctl patch
* Reviewed Zoran's suspend watchdog patchset & discussed plans for
suspend-time logging
=== Plans ===
* Get feedback from Minchan and send volatile ranges to lkml
* Probably More LPC minisummit planning
* Hopefully more ION research/discussion
=== Issues ===
* NA
Hey Kevin,
Sorry to pester you, but you've always been helpful with these sort
of questions.
I'm trying to test a pre 3.10-rc1 kernel on panda, and its hanging after
"Starting kernel ..."
3.9 boots fine, and I was curious if you had any hints as to what new
config magic I need to get things going.
Attached are my good/bad configs.
thanks
-john
This patch-set implements early printk support for virtio console devices without using any hypercalls.
The current virtio early printk code in kernel expects that hypervisor will provide some mechanism generally a hypercall to support early printk. This patch-set does not break existing hypercall based early print support.
This implementation adds:
1. Early writeonly register named early_wr in virtio console's config space.
2. Host feature flags namely VIRTIO_CONSOLE_F_EARLY_WRITE for telling guest about early-write capability in console device.
Early write mechanism:
1. When a guest wants to out some character, it has to simply write the character to early_wr register in config space of virtio console device.
Pranavkumar Sawargaonkar (2):
virtio: console: Add early writeonly register to config space
arm64: earlyprintk support for virtio-mmio console
Documentation/virtual/virtio-spec.txt | 13 ++++++++++--
arch/arm64/kernel/early_printk.c | 35 +++++++++++++++++++++++++++++++++
include/uapi/linux/virtio_console.h | 3 +++
3 files changed, 49 insertions(+), 2 deletions(-)
--
1.7.9.5
Hi,
I checked out 13.04 build and followed instructions from "Building from
suorce" tab.
https://releases.linaro.org/13.04/openembedded/aarch64/
I compiled using "bitbake linaro-image-sdk". I am getting following error.
Does anybody know what is the problem?
Thanks,
Aparna
getdents.h:60:16: note: each undeclared identifier is reported only once
for each function it appears in
| In file included from getdents01.c:57:0:
| getdents.h: In function 'getdents':
| getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this
function)
| getdents.h:60:16: note: each undeclared identifier is reported only once
for each function it appears in
| In file included from getdents03.c:56:0:
| getdents.h: In function 'getdents':
| getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this
function)
| getdents.h:60:16: note: each undeclared identifier is reported only once
for each function it appears in
| In file included from getdents02.c:53:0:
| getdents.h: In function 'getdents':In file included from
getdents04.c:56:0:
| getdents.h: In function 'getdents':
|
| getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this
function)getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in
this function)
|
| getdents.h:60:16: note: each undeclared identifier is reported only once
for each function it appears in
| getdents.h:60:16: note: each undeclared identifier is reported only once
for each function it appears in
| In file included from getdents02.c:53:0:
| getdents.h: In function 'getdents':
| getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this
function)
| getdents.h:60:16: note: each undeclared identifier is reported only once
for each function it appears in
| In file included from getdents03.c:56:0:
| getdents.h: In function 'getdents':
| getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this
function)
| getdents.h:60:16: note: each undeclared identifier is reported only once
for each function it appears in
| make[4]: *** [getdents01] Error 1
| make[4]: *** Waiting for unfinished jobs....
| make[4]: *** [getdents01_64.o] Error 1
| make[4]: *** [getdents03] Error 1
| make[4]: *** [getdents02] Error 1
| make[4]: *** [getdents04] Error 1
| In file included from getdents04.c:56:0:
| getdents.h: In function 'getdents':
| getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this
function)
| getdents.h:60:16: note: each undeclared identifier is reported only once
for each function it appears in
| make[4]: *** [getdents03_64.o] Error 1
| make[4]: *** [getdents02_64.o] Error 1
| make[4]: *** [getdents04_64.o] Error 1
| make[4]: Leaving directory
`/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel/syscalls/getdents'
| make[3]: *** [all] Error 2
| make[3]: Leaving directory
`/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel/syscalls'
| make[2]: *** [all] Error 2
| make[2]: Leaving directory
`/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel'
| make[1]: *** [all] Error 2
| make[1]: Leaving directory
`/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases'
| make: *** [testcases-all] Error 2
| ERROR: oe_runmake failed