<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/arm/include/asm/elf.h, branch linux-2.6.37.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.37.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.37.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2010-10-02T02:35:19Z</updated>
<entry>
<title>ARM: add a vma entry for the user accessible vector page</title>
<updated>2010-10-02T02:35:19Z</updated>
<author>
<name>Nicolas Pitre</name>
</author>
<published>2010-08-27T03:10:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ec706dab290c486837d4a825870ab052bf200279'/>
<id>urn:sha1:ec706dab290c486837d4a825870ab052bf200279</id>
<content type='text'>
The kernel makes the high vector page visible to user space. This page
contains (amongst others) small code segments that can be executed in
user space.  Make this page visible through ptrace and /proc/&lt;pid&gt;/mem
in order to let gdb perform code parsing needed for proper unwinding.

For example, the ERESTART_RESTARTBLOCK handler actually has a stack
frame -- it returns to a PC value stored on the user's stack.   To
unwind after a "sleep" system call was interrupted twice, GDB would
have to recognize this situation and understand that stack frame
layout -- which it currently cannot do.

We could fix this by hard-coding addresses in the vector page range into
GDB, but that isn't really portable as not all of those addresses are
guaranteed to remain stable across kernel releases.  And having the gdb
process make an exception for this page and get  content from its own
address space for it looks strange, and it is not future proof either.

Being located above PAGE_OFFSET, this vma cannot be deleted by
user space code.

Signed-off-by: Nicolas Pitre &lt;nicolas.pitre@linaro.org&gt;
</content>
</entry>
<entry>
<title>ARM: 6189/1: Add support for the MOVW/MOVT relocations in Thumb-2</title>
<updated>2010-08-05T09:35:46Z</updated>
<author>
<name>Catalin Marinas</name>
</author>
<published>2010-06-21T14:10:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8dd47741d191400c46173ed9fba9d14b4033ce23'/>
<id>urn:sha1:8dd47741d191400c46173ed9fba9d14b4033ce23</id>
<content type='text'>
The patch adds handling case for the R_ARM_THM_MOVW_ABS_NC and
R_ARM_THM_MOVT_ABS relocations in arch/arm/kernel/module.c. Such
relocations may appear in Thumb-2 compiled kernel modules.

Reported-by: Kyungmin Park &lt;kmpark@infradead.org&gt;
Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>ARM: fix build warning in asm/elf.h</title>
<updated>2010-07-26T10:29:06Z</updated>
<author>
<name>Russell King</name>
</author>
<published>2010-07-26T10:02:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=392c57a2ec811db37ae45adc513704cf92ba3e69'/>
<id>urn:sha1:392c57a2ec811db37ae45adc513704cf92ba3e69</id>
<content type='text'>
  CC      kernel/elfcore.o
In file included from include/linux/elf.h:7,
                 from kernel/elfcore.c:1:
arch/arm/include/asm/elf.h:124: warning: 'struct mm_struct' declared inside parameter list
arch/arm/include/asm/elf.h:124: warning: its scope is only this definition or declaration, which is probably not what you want

Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[ARM] implement arch_randomize_brk()</title>
<updated>2010-06-15T01:22:11Z</updated>
<author>
<name>Nicolas Pitre</name>
</author>
<published>2010-06-14T20:27:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=990cb8acf23cab19a2930f1ed5e7dc108f89079b'/>
<id>urn:sha1:990cb8acf23cab19a2930f1ed5e7dc108f89079b</id>
<content type='text'>
For this feature to take effect, CONFIG_COMPAT_BRK must be turned
off.  This can safely be turned off for any EABI user space versions.

Signed-off-by: Nicolas Pitre &lt;nicolas.pitre@linaro.org&gt;
</content>
</entry>
<entry>
<title>arch/arm/include/asm/elf.h: forward-declare the task-struct</title>
<updated>2010-05-01T10:33:00Z</updated>
<author>
<name>Andrew Morton</name>
</author>
<published>2010-04-27T21:09:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ea5ce655b90f5debb7b9768284eaafcca218ddef'/>
<id>urn:sha1:ea5ce655b90f5debb7b9768284eaafcca218ddef</id>
<content type='text'>
iop32x_defconfig:

In file included from include/linux/elf.h:7,
                 from kernel/elfcore.c:1:
arch/arm/include/asm/elf.h:101: warning: "struct task_struct" declared inside parameter list
arch/arm/include/asm/elf.h:101: warning: its scope is only this definition or declaration, which is probably not what you want

Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>ARM: 5987/1: fix warning in kernel/elfcore.c from ARM's elf.h</title>
<updated>2010-03-13T10:48:22Z</updated>
<author>
<name>Mikael Pettersson</name>
</author>
<published>2010-03-11T11:28:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bb35579b45bcb0b74167a2165d3ea973f640bf00'/>
<id>urn:sha1:bb35579b45bcb0b74167a2165d3ea973f640bf00</id>
<content type='text'>
2.6.34-rc1 added kernel/elfcore.c which includes &lt;asm/elf.h&gt;.
On ARM, this results in:

In file included from include/linux/elf.h:7,
                 from kernel/elfcore.c:1:
/tmp/linux-2.6.34-rc1/arch/arm/include/asm/elf.h:101: warning: 'struct task_struct' declared inside parameter list
/tmp/linux-2.6.34-rc1/arch/arm/include/asm/elf.h:101: warning: its scope is only this definition or declaration, which is probably not what you want

Including &lt;linux/sched.h&gt; seems a bit heavyweight, so this patch just
adds a tentative declaration of struct task_struct in &lt;asm/elf.h&gt;.

Signed-off-by: Mikael Pettersson &lt;mikpe@it.uu.se&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>elf: kill USE_ELF_CORE_DUMP</title>
<updated>2009-12-16T15:20:12Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2009-12-16T00:47:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=698ba7b5a3a7be772922340fade365c675b8243f'/>
<id>urn:sha1:698ba7b5a3a7be772922340fade365c675b8243f</id>
<content type='text'>
Currently all architectures but microblaze unconditionally define
USE_ELF_CORE_DUMP.  The microblaze omission seems like an error to me, so
let's kill this ifdef and make sure we are the same everywhere.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Acked-by: Hugh Dickins &lt;hugh.dickins@tiscali.co.uk&gt;
Cc: &lt;linux-arch@vger.kernel.org&gt;
Cc: Michal Simek &lt;michal.simek@petalogix.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>ARM: 5759/1: Add register information of threads to coredump</title>
<updated>2009-10-14T09:33:05Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2009-10-13T07:54:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cde3f8607350666c4dd120dbbdbd9c70ffb2ea61'/>
<id>urn:sha1:cde3f8607350666c4dd120dbbdbd9c70ffb2ea61</id>
<content type='text'>
Defines ELF_CORE_COPY_TASK_REGS so that CPU register information
of every thread is included in coredump. Without this, only the faulting
thread is coredumped.

Cc: Roger Quadros &lt;ext-roger.quadros@nokia.com&gt;
Cc: linux-arm-kernel@lists.infradead.org
Signed-off-by: Mika Westerberg &lt;mika.westerberg@iki.fi&gt;
Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@nokia.com&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>Thumb-2: Add support for loadable modules</title>
<updated>2009-07-24T11:32:59Z</updated>
<author>
<name>Catalin Marinas</name>
</author>
<published>2009-07-24T11:32:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=adca6dc23bc620ea95392659625200a252b97be3'/>
<id>urn:sha1:adca6dc23bc620ea95392659625200a252b97be3</id>
<content type='text'>
Modules compiled to Thumb-2 have two additional relocations needing to
be resolved at load time, R_ARM_THM_CALL and R_ARM_THM_JUMP24, for BL
and B.W instructions. The maximum Thumb-2 addressing range is +/-2^24
(+/-16MB) therefore the MODULES_VADDR macro in asm/memory.h is set to
(MODULES_END - 8MB) for the Thumb-2 compiled kernel.

Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;
</content>
</entry>
<entry>
<title>[ARM] 5507/1: support R_ARM_MOVW_ABS_NC and MOVT_ABS relocation types</title>
<updated>2009-05-07T16:21:01Z</updated>
<author>
<name>Paul Gortmaker</name>
</author>
<published>2009-05-07T15:18:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ae51e609843f7d0aaeb1c2ad9f89d252a4899885'/>
<id>urn:sha1:ae51e609843f7d0aaeb1c2ad9f89d252a4899885</id>
<content type='text'>
From: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;

To fully support the armv7-a instruction set/optimizations, support
for the R_ARM_MOVW_ABS_NC and R_ARM_MOVT_ABS relocation types is
required.

The MOVW and MOVT are both load-immediate instructions, MOVW loads 16
bits into the bottom half of a register, and MOVT loads 16 bits into the
top half of a register.

The relocation information for these instructions has a full 32 bit
value, plus an addend which is stored in the 16 immediate bits in the
instruction itself.  The immediate bits in the instruction are not
contiguous (the register # splits it into a 4 bit and 12 bit value),
so the addend has to be extracted accordingly and added to the value.
The value is then split and put into the instruction; a MOVW uses the
bottom 16 bits of the value, and a MOVT uses the top 16 bits.

Signed-off-by: David Borman &lt;david.borman@windriver.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
</feed>
