From: Sreeni <sreeni.pulichi@gmail.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory Management during Program Loading
Date: Tue, 28 Jun 2005 14:12:43 -0400 [thread overview]
Message-ID: <94e67edf0506281112545d4766@mail.gmail.com> (raw)
In-Reply-To: <200506281800.j5SI0FEe011475@turing-police.cc.vt.edu>
Thanks you Valdis for your reply.
We have a "Bus Monitor hardware" which monitors and polices the bus at
the specified physical address.
Basically we need to run "secure" program under the supervision of the
Bus monitor hardware.
Kernel can see the "secure" memory region, and kernel is reponsible for enabling
the "Bus monitor Hardware".
Thanks,
Sreeni
On 6/28/05, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> On Tue, 28 Jun 2005 13:49:46 EDT, Sreeni said:
> > In our system we have a secure physical memory starting and ending at
> > predefined addresses. We want to execute certain programs, which have
> > to be running secure in those address spaces only.
>
> Can you explain how this memory is "secure", and how you expect a kernel that's
> running *outside* this secure space to load a program into it?
>
> > Is it possible to force the loader to load the "particular" program
> > (both the code and data segment) at that pre-defined secure physical
> > memory, without any major kernel changes?
>
> It's more complicated than that - not only do you need to worry about running
> the program in that space, you also need to worry about things like malloc()
> space for the program, I/O buffers, and so on.....
>
>
>
--
~Sreeni
-iDream
next prev parent reply other threads:[~2005-06-28 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 17:49 Memory Management during Program Loading Sreeni
2005-06-28 18:00 ` Valdis.Kletnieks
2005-06-28 18:12 ` Sreeni [this message]
2005-06-28 18:58 ` Valdis.Kletnieks
2005-06-28 19:09 ` Sreeni
[not found] ` <94e67edf050628122441f6178@mail.gmail.com>
2005-06-28 20:13 ` Sreeni
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=94e67edf0506281112545d4766@mail.gmail.com \
--to=sreeni.pulichi@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.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