Re: Mapping memory into process address space

2014-08-28 Thread Björn Döbel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.08.2014 06:33, Noah Zentzis wrote: On 08/21/2014 02:14 PM, Adam Lackorzynski wrote: Yes, you'd need to create a new region mapper for the new task, one that knows about the virtual address space layout of that one. Should be possible by

Re: Mapping memory into process address space

2014-08-27 Thread Noah Zentzis
On 08/21/2014 02:14 PM, Adam Lackorzynski wrote: Yes, you'd need to create a new region mapper for the new task, one that knows about the virtual address space layout of that one. Should be possible by using a new instance of Region_map as done in the l4re_kernel.You'll also need to create an

Re: Mapping memory into process address space

2014-08-21 Thread Adam Lackorzynski
On Tue Aug 19, 2014 at 20:59:16 -0700, Noah Zentzis wrote: On 08/17/2014 12:55 AM, Adam Lackorzynski wrote: So now I'm not sure how you want to proceed. Are your programs special ones, i.e. that they are quite different from L4 programs or are they L4 programs? I wondering where to do the

Re: Mapping memory into process address space

2014-08-19 Thread Björn Döbel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Also, do not call the allocator twice within the function call, because then you would obtain two different dataspaces and this is not what you want here. Better do L4:CapDataspace x = L4Re::Util::cap_alloc.allocL4::Dataspace(); long alloc =

Re: Mapping memory into process address space

2014-08-15 Thread Björn Döbel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 printf(This message is printed\n); task-map(L4Re::This_task, env-mem_alloc().fpage(), env-mem_alloc().snd_base()); printf(This message is never printed\n); env-mem_alloc() only gives you the memory allocator. You will have to call

Mapping memory into process address space

2014-08-14 Thread Noah Zentzis
I don't want to use libloader because I'm trying to create a new process with dynamically-generated assembly (and alter it while the process is running), so I can't really output an ELF binary. On 08/18/2014 08:50, Björn

Re: Mapping memory into process address space

2014-08-14 Thread Adam Lackorzynski
On Thu Aug 14, 2014 at 01:22:31 -0700, Noah Zentzis wrote: I don't want to use libloader because I'm trying to create a new process with dynamically-generated assembly (and alter it while the process is running), so I

Re: Mapping memory into process address space

2014-08-14 Thread Noah Zentzis
On 08/14/2014 03:01 PM, Adam Lackorzynski wrote: Typical arguments for L4::Task::map for memory are (omitting cache attributes etc.): l4_msgtag_t t; t = dst_task-map(src_task, l4_fpage(src_address, L4_PAGESHIFT, L4_FPAGE_RWX), dst_address);

Re: Mapping memory into process address space

2014-08-13 Thread Björn Döbel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13.08.2014 04:26, Noah Zentzis wrote: I'm trying to launch a new process (without libloader) and I'm having trouble mapping memory to it. I've found the prog_attach_ds and prog_reserve_utcb_area methods in libloader and ned, but I'm not sure