Allow arches to write the opcode with a custom function. ARM needs to
customize the swbp instruction depending on the condition code of the
instruction it replaces.
Signed-off-by: Rabin Vincent
Signed-off-by: David A. Long
---
include/linux/uprobes.h | 3 +++
kernel/events/uprobes.c | 16
Add a weak function for any architecture-specific initialization. ARM
will use this to register the handlers for the undefined instructions it
uses to implement uprobes.
Signed-off-by: Rabin Vincent
Signed-off-by: David A. Long
---
include/linux/uprobes.h | 1 +
kernel/events/uprobes.c | 10 +
Using Rabin Vincent's ARM uprobes patches as a base, enable uprobes
support on ARM.
Caveats:
- Thumb is not supported
- XOL abort/trap handling is not implemented
Signed-off-by: David A. Long
---
arch/arm/Kconfig | 4 +
arch/arm/include/asm/ptrace.h | 6 +
arch/arm
Allow arches to customize how the instruction is filled into the xol
slot. ARM will use this to insert an undefined instruction after the
real instruction in order to simulate a single step of the instruction
without hardware support.
Signed-off-by: Rabin Vincent
Signed-off-by: David A. Long
-
Allow arches to decided to ignore a probe hit. ARM will use this to
only call handlers if the conditions to execute a conditionally executed
instruction are satisfied.
Upleveled for v3.10.
Signed-off-by: David A. Long
---
include/linux/uprobes.h | 1 +
kernel/events/uprobes.c | 17 ++
This patch series adds basic uprobes support to ARM. It is based on patches
developed earlier by Rabin Vincent. That approach of adding special cases into
the kprobes instruction parsing code was not well received. This approach
separates the ARM instruction parsing code in kprobes out into a
It seems odd to keep the function declarations in the arch header where
they will need to be copy/pasted verbatim across arches. Move them to
the common header.
Signed-off-by: Rabin Vincent
Signed-off-by: David A. Long
---
arch/x86/include/asm/uprobes.h | 7 ---
include/linux/uprobes.h
On 06/04/13 04:10, Jon Medhurst (Tixy) wrote:
What are the actual errors you get? What kernel config are you using? Do
you have these options enabled?
The errors are:
mmc0: host doesn't support card's voltages
mmc0: error -22 whilst initialising SD card
SD: Unknown CMD1
The above repeats qu
I'm trying to build for versatile express to run under QEMU. When I
boot under QEMU I get errors regarding the SD voltage, and it fails. I
have not really used QEMU for testing before. Has anyone encountered
this? It's likely I've got something basic wrong. Here is the command
I'm using:
On Thu, 2012-03-01 at 16:59 +, Turgis, Frederic wrote:
> Wrong Dave, I meant Dave Long ;-)
>
> OMAP Platform Business Unit - OMAP System Engineering - Platform Enablement -
> System Multimedia
>
>
> > Hi Dave,
> >
> > By the way, in
> > http://lists.linaro.org/pipermail/linaro-dev/2011-Sep
On Tue, 2011-09-27 at 16:29 +0300, Siarhei Siamashka wrote:
> Please just do something :) I don't see why you can't supply the
> kernels with oprofile working in timer mode with a usable sampling
> frequency *right now*. That should be enough for the helpless users
> who can't or don't want to tw
Andy made an interesting suggestion to me. What if the profile event
code allocated all the counters to the requested event. It could
reallocate half of them if a second event was also requested, and so on,
till we're down to one (unreliably interrupting) counter. Or we could
set a limit requiri
On Fri, 2011-09-16 at 11:30 +0200, Bianconi, Cyril wrote:
> I don't think that the A9 issue is the same as the A8. However,
> effects are the same i.e. it's hard to use PMU.
>
> I cannot communicate the A9 errata document as-is due to legal stuff
> but I belive that I can explain the issue.
> The
>Sorry, who is working on this and when is it going back in? perf is a
>significant feature and Panda is a very common board...
>
>-- Michael
I have been unable to reproduce the boot hang problem after unreverting
the interrupt patch. Can those experiencing it please verify they are
using the l
>These days, I believe the separate oprofile backend for ARM has gone
>away, and oprofile is implemented using the perf backend anyway.
I've been asked to look into this some more. I will post what I learn.
-dl
___
linaro-dev mailing list
linaro-dev@
On Sat, 2011-08-20 at 08:01 +0200, Albert ARIBAUD wrote:
> What exactly prevents ARM Linux from booting when FDT or initrd are
> above 768MB? Can this limitation not be lifter on the Linux side?
I don't think it reasonably can be.
I have to start by saying that I am in no way a Linux VM expe
Reserve any memory above 768MB to prevent u-boot from relocating fdt or initrd
data into memory that Linux cannot reference during early boot. Code taken (with
modifications) from the powerpc bootm.c.
Signed-off-by: David A. Long
---
arch/arm/lib/bootm.c | 24 +++-
1 files
> As I understand it, btrfs is considered OK for file systems running on
> systems that don't suffer from power failure, so for writing an image
> and testing it this should be fine.
>
> So, what do people think about switching?
I too would be considered about filesystem integrity given the nu
On Wed, 2011-07-27 at 21:45 +0100, Andy Green wrote:
>
> Shawn Guo helped me before with this magic required sequencing to get
> the dtbs built:
Thanks. The problem was that flattened device tree was not set in my
config file. I really thought we had this set in the panda default
config fil
On Tue, 2011-06-21 at 12:25 -0600, Grant Likely wrote:
> On Tue, Jun 21, 2011 at 11:31 AM, David Long wrote:
> >
> > Hi,
> >
> > WRT to .dtb files: I see sources in the kernel tree but they don't appear
> > to be built as part of the kernel build. How
On Thu, 2011-07-14 at 20:53 -0600, Grant Likely wrote:
>You should have everything you need to fix it. If
> CONFIG_SYS_BOOTMAPSZ is defined, then U-Boot will not use memory
> larger that that for the dtb or atags.
>
> Right now CONFIG_SYS_BOOTMAPSZ is not set by default, but we could
> default i
On Thu, 2011-07-14 at 15:21 -0500, Scott Wood wrote:
> You have memory below where the kernel is loaded?
Our boot script loads the kernel 2MB into physical RAM. It loads the
initrd and fdt from the same NAND flash file system into RAM below that.
When we boot without specifying an FDT, u-boot
On Thu, 2011-07-14 at 14:43 -0500, Scott Wood wrote:
> You need to use lmb_reserve() to exclude any memory regions that are not
> suitable for boot images -- see powerpc's arch_lmb_reserve() and
> get_effective_memsize()/CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE.
If one excludes HIGHMEM from the area u-
On Fri, 2011-07-15 at 03:50 +0900, Grant Likely wrote:
> Regardless of this patch, the pandaboard uboot still needs to be
> fixed. Setting an fdt_high variable is useful for debug, but it is not
> a fix.
>
Then someone needs to own the issue of stopping the current u-boot
default behavior of
On Thu, 2011-07-14 at 09:10 -0400, Jerry Van Baren wrote:
> Hi Dave,
>
> This looks reasonable, with one minor nit...
>
> Need spaces around the "="
>
> I will add the spaces before applying the patch unless you send an
> updated patch.
>
OK, thanks much. Someone else recently pointed t
Can someone explain why uboot copies the initrd and device tree data to
higher memory when we boot panda with a dtb? I'm assuming there's a
reason, but it seems a problematic thing to do (potentially even without
>3/4GB SDRAM present).
-dl
___
linaro-
26 matches
Mail list logo
