diff options
| author | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2020-07-05 16:12:09 +0200 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2020-07-05 16:12:09 +0200 |
| commit | b71710cd519c7f9010b770af8bb3943010476476 (patch) | |
| tree | 004ee494c0a5d7756d3558f8b50f57487e14f763 | |
| parent | 640b447be65d4cbdafa3b7f9c4317fd8d9a6ae33 (diff) | |
Making vm_allocate_contiguous return a memory object is not really a priority
| -rw-r--r-- | include/mach/mach.defs | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/include/mach/mach.defs b/include/mach/mach.defs index 77cc7d49..a4e23db6 100644 --- a/include/mach/mach.defs +++ b/include/mach/mach.defs @@ -738,12 +738,12 @@ case. Minimum and maximum addresses and alignment should do. Maybe boundary crossing but usually, specifying the right alignment and size is enough. -For upstream -inclusion, we need to do it properly: the RPC should return a special +Ideally we could make the RPC should return a special memory object (similar to device_map() ), which can then be mapped into the process address space with vm_map() like any other memory object. +But we currently do not need it, if we really do we can introduce another RPC. -phys_address_t? +FIXME: use phys_address_t */ routine vm_allocate_contiguous( host_priv : host_priv_t; |