[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PCI arbiter memory mapping
From: |
Joan Lledó |
Subject: |
Re: PCI arbiter memory mapping |
Date: |
Wed, 18 Aug 2021 19:34:05 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 |
El 18/8/21 a les 0:13, Sergey Bugaev ha escrit:
you can no longer get the underlying memory object with vm_region ()
How so? reading the docs I understood it does:
https://www.gnu.org/software/hurd/gnumach-doc/Memory-Attributes.html
"The port object_name identifies the memory object associated with this
region"
(Well in fact what actually changed is that gnumach at some point
allowed the use of "memory object name ports" in vm_map (), and now
once again doesn't.
vm_map does receive the memory object as parameter:
https://www.gnu.org/software/hurd/gnumach-doc/Mapping-Memory-Objects.html
"memory_object is the port that represents the memory object: used by
user tasks in vm_map"
It never allowed you to get the actual memory
object.)
vm_map receives a memory object, doesn't return it
- Re: PCI arbiter memory mapping, (continued)
- Re: PCI arbiter memory mapping, Joan Lledó, 2021/08/17
- Re: PCI arbiter memory mapping, Sergey Bugaev, 2021/08/17
- Re: PCI arbiter memory mapping, Joan Lledó, 2021/08/18
- Re: PCI arbiter memory mapping, Sergey Bugaev, 2021/08/18
- Re: PCI arbiter memory mapping, Joan Lledó, 2021/08/17
- Re: PCI arbiter memory mapping, Sergey Bugaev, 2021/08/17
- Re: PCI arbiter memory mapping,
Joan Lledó <=
- Re: PCI arbiter memory mapping, Sergey Bugaev, 2021/08/18
Re: PCI arbiter memory mapping, Samuel Thibault, 2021/08/09