From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sandbox: Add improved RAM simulation
Date: Tue, 1 Nov 2011 14:52:32 -0400 [thread overview]
Message-ID: <201111011452.33518.vapier@gentoo.org> (raw)
In-Reply-To: <4EB03C64.3010102@arcor.de>
On Tuesday 01 November 2011 14:37:24 Matthias Weisser wrote:
> I don't know the memory layout strategies for all the Linux/Unix variant
> out there. But typically text/bss/data is in the lower address range
> (some megs above 0) and in the upper range (right under kernel space)
> there is space used for stack and shared objects. Even with ASLR the
> address I used in the patch should be mappable.
relying on any address layout behavior is doomed to fail. and in this case,
it's unnecessary. so let's not bother.
> >>> also, with Simon's other patch to md to use the remap func, the address
> >>> of our memory backing store doesn't matter.
> >>
> >> Well, you are right. But with the posted patch you don't need any remap
> >> function and md/mm/mtest/mw works out of the box.
> >
> > This is interesting. What is the test purpose of specifying a
> > particular virtual address for your memory?
>
> Emulating the behavior of a u-boot on real hardware as close as
> possible. We have some chunk of memory at a given location. Thats it.
> With a minimum of additional work we can also simulate additional banks
> of RAM using multiple mmaps.
adding a CONFIG knob to control the virtual address of the memory is fine
> > If this is useful then we should make the mmap function fail if it
> > cannot honour the address, since otherwise presumably some tests will
> > fail.
>
> Maybe. But on the other hand tests can always extract the actual address
> of RAM from gd->bd->bi_dram[0].start. If test use these address we can
> abandon the use of of fixed address. But I still thinks its nice to have
> an aligned address of RAM start as this is what we have on (all?) real
> hardware.
i'd rather see bi_dram die than extend it. if you want to utilize the virtual
memory, let's use the already existing map helper.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20111101/51e15d18/attachment.pgp
next prev parent reply other threads:[~2011-11-01 18:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 14:07 [U-Boot] [PATCH] sandbox: Add improved RAM simulation Matthias Weisser
2011-11-01 15:28 ` Mike Frysinger
2011-11-01 16:05 ` Matthias Weisser
2011-11-01 16:45 ` Simon Glass
2011-11-01 18:37 ` Matthias Weisser
2011-11-01 18:52 ` Mike Frysinger [this message]
2011-11-01 19:01 ` Matthias Weisser
2011-11-01 20:10 ` Mike Frysinger
2011-11-02 18:35 ` Matthias Weisser
2011-11-02 19:20 ` Mike Frysinger
2011-11-01 17:12 ` Mike Frysinger
2011-11-01 16:42 ` Simon Glass
2011-11-02 20:12 ` [U-Boot] [[PATCH V2]] " Matthias Weisser
2011-11-02 20:39 ` Mike Frysinger
2011-11-02 20:56 ` Simon Glass
2011-11-03 17:55 ` Matthias Weisser
2011-11-03 18:02 ` [U-Boot] [PATCH V3] " Matthias Weisser
2011-11-03 18:05 ` Mike Frysinger
2011-11-03 22:55 ` Simon Glass
2011-11-05 10:40 ` [U-Boot] [PATCH V4] " Matthias Weisser
2011-11-05 15:05 ` Simon Glass
2011-11-05 16:47 ` Mike Frysinger
2011-12-02 17:08 ` 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=201111011452.33518.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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