You can also "access" private data in kernel address space from user mode
programs, by employing a simple trick. A user program can request access to
a section of private kernel address space (via fifos, shared memory, or
whatever). Then a kernel module can copy the requested section of the kernel
private address space "needed in user space" into shared memory. Then user
mode program can view/modify the shared memory area and signal/indicate the
change(s) made. Finally the kernel module can take care of "updating" the
changes back into the kernel private address space (from the shared memory
area).
I was able to implement a similar "swapping technique" in my simulator
application. It allows access to ALL kernel real-time storage from the user
side as well...
Regards,
Todd Gearheart
-----Original Message-----
From: Stuart Hughes [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 07, 2001 7:43 AM
To: Stefano Picerno
Cc: [EMAIL PROTECTED]
Subject: Re: [rtl] beginner question
Stefano Picerno wrote:
>
> If I have two different realtime modules, can I access the address space
> of one of them from the other?
>
> I mean, if task A have some private data at 0x1234578, can task B read the
> same data at the same address?
Yes, they occupy the same kernel address space.
Regards, Stuart
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
