El 17/10/21 a les 18:32, Samuel Thibault ha escrit> It will be useful to
implement mremap with the same call.
In your case you know the size, don't you?
Yes
That's almost the same, isn't it? (there is just the max_prot parameter,
which you can indeed add to the RPC above).
It's similar b
Sergey Bugaev, le dim. 17 oct. 2021 22:10:38 +0300, a ecrit:
> On Sun, Oct 17, 2021 at 6:41 PM Joan Lledó wrote:
> > Why the "size" parameter? I'd rather see a new wrapper for
> > memory_object_create_proxy() which receives the same params but with the
> > address instead of the original pager, wh
On Sun, Oct 17, 2021 at 6:41 PM Joan Lledó wrote:
> Why the "size" parameter? I'd rather see a new wrapper for
> memory_object_create_proxy() which receives the same params but with the
> address instead of the original pager, which internally gets the pager
> from the address and calls memory_obj
Joan Lledó, le dim. 17 oct. 2021 17:41:11 +0200, a ecrit:
> El 16/10/21 a les 13:27, Sergey Bugaev ha escrit:
> > routine vm_make_proxy (
> > target_task : vm_task_t;
> > address : vm_address_t;
> > size : vm_size_t;
> > out proxy : memory_object_t);
>
> Why the "size" paramete
Hi,
El 16/10/21 a les 13:27, Sergey Bugaev ha escrit:
routine vm_make_proxy (
target_task : vm_task_t;
address : vm_address_t;
size : vm_size_t;
out proxy : memory_object_t);
Why the "size" parameter? I'd rather see a new wrapper for
memory_object_create_proxy() which re
