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, [email protected] <[email protected]> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
