[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issues with remap when using a nested pci arbiter
|
From: |
Joan Lledó |
|
Subject: |
Re: Issues with remap when using a nested pci arbiter |
|
Date: |
Tue, 10 Dec 2019 17:42:58 +0100 (CET) |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 |
Hi,
El 8/12/19 a les 14:49, Samuel Thibault ha escrit:
> Hello,
>
> Joan Lledó via Bug reports for the GNU Hurd, le dim. 08 déc. 2019 09:04:09
> +0100, a ecrit:
>> demo@debian:~$ remap /servers/bus/pci /home/jlledom/gnu/servers/bus/pci
>> -- rpctrace -o /home/demo/demo.log env
>> LD_LIBRARY_PATH=/home/jlledom/gnu/lib /home/jlledom/gnu/bin/lspci
>>
>> After this, I can see in the rpc trace that RPCs are being sent to the
>> main arbiter. Any idea on why this happens?
>
> rpctrace shows you what the program is doing. It would indeed request
> servers/bus/pci from its root. But here the root is the remap
> translator, which will remap that before actually providing a port.
>
> Samuel
>
Sorry, I said I observed the remap problem in the rpc trace, but I
observed it in the client's behavior. When running lspci with remap, I
can see it returns the devices configured by the main arbiter, not the
nested one, just attached the rpc trace to add debug info.
The thing is the remap is not working, is there something I'm doing wrong?