[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bd0f97a0912070210m4f13e174y154fc82732ef136c@mail.gmail.com>
Date: Mon, 7 Dec 2009 05:10:11 -0500
From: Mike Frysinger <vapier.adi@...il.com>
To: Jie Zhang <jie.zhang@...log.com>
Cc: David Howells <dhowells@...hat.com>,
uClinux development list <uclinux-dev@...inux.org>,
linux-kernel@...r.kernel.org, Greg Ungerer <gerg@...inux.org>,
uclinux-dist-devel@...ckfin.uclinux.org,
David McCullough <davidm@...pgear.com>
Subject: Re: [uClinux-dev] [PATCH/RFC] FDPIC: add hook for arches to customize
program header parsing
On Fri, Dec 4, 2009 at 19:28, Jie Zhang <wrote:
> On 12/05/2009 01:44 AM, David Howells wrote:
>> Mike Frysinger<vapier@...too.org> wrote:
>>> The Blackfin port has custom program header flags/addresses for
>>> automatically loading regions into the dedicated on-chip SRAM. So add a
>>> hook for ports to leverage.
>>
>> Now that I've ACK'd this, I feel I'm going to have to NAK it. I'm not
>> against
>> the general concept, but:
>>
>>> + do_munmap(mm, *maddr, phdr->p_memsz + *disp);
>>
>> There needs to be a mapping covering the SRAM region for the purposes of
>> the
>
> Our GDB is still lack of the feature to debug applications using SRAM.
semi true. L1 text appears to work fine:
(gdb) stepi
0xffa02aac in moo ()
(gdb) dis
Dump of assembler code from 0xffa02aac to 0xffa02aec:
0xffa02aac <moo+0>: LINK 0xc; /* (12) */
0xffa02ab0 <moo+4>: [FP + 0x8] = R0;
....
but L1 data doesnt seem to work (probably something simple to fix in
our kernel ptrace?):
(gdb) print i
Cannot access memory at address 0xff803e58
the simple code:
int i __attribute__((l1_data));
> So this part of code was not got exercised. So if we remove this line, can
> this patch got merged?
this code does get exercised -- it's run every time code is loaded
from initramfs for example. the
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists