mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier.adi@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: Jie Zhang <jie.zhang@analog.com>,
	uClinux development list <uclinux-dev@uclinux.org>,
	linux-kernel@vger.kernel.org, Greg Ungerer <gerg@uclinux.org>,
	uclinux-dist-devel@blackfin.uclinux.org,
	David McCullough <davidm@snapgear.com>
Subject: Re: [uClinux-dev] [PATCH/RFC] FDPIC: add hook for arches to customize  program header parsing
Date: Mon, 7 Dec 2009 05:09:55 -0500	[thread overview]
Message-ID: <8bd0f97a0912070209k5c87643cm53a24566f7e63a9f@mail.gmail.com> (raw)
In-Reply-To: <643.1260026074@redhat.com>

On Sat, Dec 5, 2009 at 10:14, David Howells wrote:
> Jie Zhang <jie.zhang@analog.com> wrote:
>> > 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. So this
>> part of code was not got exercised. So if we remove this line, can this patch
>> got merged?
>
> No.  Firstly, the piece of storage that gets munmapped isn't used, so unmapping
> it isn't wrong.  What you need to do is to put a mapping over the bit of the
> SRAM you wish to use and then fill it and use it.  Ideally, you'd do this
> inside of do_mmap_pgoff() - that way those bits of the SRAM can be shared, but
> I'm not sure how best to do that.

we've looked into trying to represent the SRAM regions with normal
VMA's a few times, but i think the conclusion every time has been that
it isnt [currently] doable.  i vaguely recall it's due to the fact
that Blackfin SRAM is harvard based and VMA's cant cope with this
restriction.  Sonic should be able to provide more details though.

currently we have a simpler allocator for kernel/user space to
leverage so that small pieces can be dynamically allocated/freed.

> But you need to stick a VMA over it so that various checks don't spit
> EFAULT/EIO at you.

we give SRAM's a "pass" in every place where addresses are checked
-mike

  reply	other threads:[~2009-12-07 10:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-13  1:01 Mike Frysinger
2009-06-13 12:23 ` [uClinux-dev] " David Howells
2009-06-13 16:13 ` Jamie Lokier
2009-06-13 16:40   ` Mike Frysinger
2009-06-13 18:25     ` Jamie Lokier
2009-06-13 18:26       ` Jamie Lokier
2009-06-14  0:32       ` Mike Frysinger
2009-06-14  0:42         ` Jie Zhang
2009-06-14  9:43 ` Paul Mundt
2009-06-15  1:43 ` Greg Ungerer
2009-06-16  8:24 ` [PATCH] " Mike Frysinger
2009-06-23  5:32   ` Andrew Morton
2009-06-23 11:04     ` Mike Frysinger
2009-12-04 17:44 ` [uClinux-dev] [PATCH/RFC] " David Howells
2009-12-05  0:28   ` Jie Zhang
2009-12-07  3:27     ` [Uclinux-dist-devel] " Zhang, Sonic
2009-12-07 10:10     ` Mike Frysinger
2009-12-07 10:17       ` Jie Zhang
2009-12-05 15:14   ` David Howells
2009-12-07 10:09     ` Mike Frysinger [this message]
2009-12-07 10:10   ` Mike Frysinger

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=8bd0f97a0912070209k5c87643cm53a24566f7e63a9f@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=davidm@snapgear.com \
    --cc=dhowells@redhat.com \
    --cc=gerg@uclinux.org \
    --cc=jie.zhang@analog.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uclinux-dev@uclinux.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®