[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Almost working pci-arbiter with rumpdisk

From: Damien Zammit
Subject: Re: Almost working pci-arbiter with rumpdisk
Date: Tue, 9 Feb 2021 21:42:29 +1100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0

On 9/2/21 5:33 am, Samuel Thibault wrote:
> Damien Zammit, le lun. 08 févr. 2021 20:33:16 +1100, a ecrit:
>> I'm getting very close to working pci + rump.
> Did you manage to find answers to your previous questions?
> (I have to admit I didn't have time to dive into them)

I managed to remove the chicken/egg problem by not requiring the underlying 
node for pcifs.

However, I'm still getting very stuck because I don't seem to have a 
"bootstrap" port for fsys_startup() in netfs for pci startup.
Where would the bootstrap port come from to do the arbiter netfs_startup -> 
As the arbiter netfs IS the bootstrap filesystem, bootstrap is NULL, or am I 

Do I need to implement some kind of netfs_S_fsys_* ?

Hurd bootstrap pci PCI machdev done
PCI netfs done
PCI maptime done
PCI pci_system_init done
XXX bootstrap is NULL
pci-arbiter: Translator startup failure: fsys_startup: (ipc/send) invalid 
destination port 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]