Re: Almost working pci-arbiter with rumpdisk

2021-02-28 Thread Samuel Thibault
Damien Zammit, le dim. 28 févr. 2021 13:27:49 +1100, a ecrit: > On 25/2/21 9:30 am, Samuel Thibault wrote: > > From reading the libnetfs/dir-readdir.c source and > > pci-arbiter/netfs_impl.c source I don't see anything obvious. Probably > > some prints in there would allow to make sure how far it i

Re: Almost working pci-arbiter with rumpdisk

2021-02-27 Thread Damien Zammit
Hi, On 25/2/21 9:30 am, Samuel Thibault wrote: > From reading the libnetfs/dir-readdir.c source and > pci-arbiter/netfs_impl.c source I don't see anything obvious. Probably > some prints in there would allow to make sure how far it is going > actually. I got past a hang, by installing the port re

Re: Almost working pci-arbiter with rumpdisk

2021-02-24 Thread Samuel Thibault
Damien Zammit, le mer. 24 févr. 2021 22:35:40 +1100, a ecrit: > On 21/2/21 9:21 pm, Samuel Thibault wrote: > > Mmm. I guess that's missing _hurd_init initialization. It would > > be tricky to separate out the really basic pieces from proc/auth > > initialization, I'd say it will be a lot less trick

Re: Almost working pci-arbiter with rumpdisk

2021-02-24 Thread Samuel Thibault
Damien Zammit, le mer. 24 févr. 2021 22:35:40 +1100, a ecrit: > On 21/2/21 9:21 pm, Samuel Thibault wrote: > > Mmm. I guess that's missing _hurd_init initialization. It would > > be tricky to separate out the really basic pieces from proc/auth > > initialization, I'd say it will be a lot less trick

Re: Almost working pci-arbiter with rumpdisk

2021-02-24 Thread Damien Zammit
On 21/2/21 9:21 pm, Samuel Thibault wrote: > Mmm. I guess that's missing _hurd_init initialization. It would > be tricky to separate out the really basic pieces from proc/auth > initialization, I'd say it will be a lot less tricky to just make > hurd_pci.c use the dir_readdir RPC directly on the ro

Re: Almost working pci-arbiter with rumpdisk

2021-02-21 Thread Samuel Thibault
Hello, Damien Zammit, le dim. 21 févr. 2021 17:00:32 +1100, a ecrit: > > ? once libpciaccess gets a port on pci-arbiter's root, it can use > > file_name_lookup_under to open directories and files in it. libnetfs > > will want to check permissions, but it could be made to accept anything > > when a

Re: Almost working pci-arbiter with rumpdisk

2021-02-20 Thread Damien Zammit
Hi, On 21/2/21 12:24 pm, Samuel Thibault wrote: > Ah, possibly. Perhaps you could make libnetfs to accept any access when > auth/proc are not available Done this! > ? once libpciaccess gets a port on pci-arbiter's root, it can use > file_name_lookup_under to open directories and files in it. lib

Re: Almost working pci-arbiter with rumpdisk

2021-02-20 Thread Samuel Thibault
Damien Zammit, le dim. 21 févr. 2021 12:15:11 +1100, a ecrit: > On 20/2/21 10:16 pm, Samuel Thibault wrote: > > It's hard to tell exactly without seeing what exactly you have done > > already. As I wrote before, device_open should return a port to the > > root directory of the pci-arbiter tree. I'm

Re: Almost working pci-arbiter with rumpdisk

2021-02-20 Thread Damien Zammit
Hi Samuel, On 20/2/21 10:16 pm, Samuel Thibault wrote: > It's hard to tell exactly without seeing what exactly you have done > already. As I wrote before, device_open should return a port to the > root directory of the pci-arbiter tree. I'm not sure exactly what you > wrote to achieve that. I thi

Re: Almost working pci-arbiter with rumpdisk

2021-02-20 Thread Samuel Thibault
Hello, Damien Zammit, le sam. 20 févr. 2021 19:45:43 +1100, a ecrit: > Ok so the problem is that its returning ENODIR on the file_name_lookup_under > call. > How do I get the root filesystem of pci arbiter to exist so it can look up > paths on the hurd pci arbiter > before rumpdisk initiates the

Re: Almost working pci-arbiter with rumpdisk

2021-02-20 Thread Damien Zammit
Ok so the problem is that its returning ENODIR on the file_name_lookup_under call. How do I get the root filesystem of pci arbiter to exist so it can look up paths on the hurd pci arbiter before rumpdisk initiates the disk driver? Do I need to call fsys_getroot somewhere in the arbiter? pci0 at

Re: Almost working pci-arbiter with rumpdisk

2021-02-19 Thread Damien Zammit
I'm getting some issue with libpciaccess, I changed it locally to detect the pci port from device_open and it seems to be opening the right port, but there must be a bug with it. I must be pretty close now, because the arbiter opens the x86 method and rump opens the hurd method of pciaccess: sta

Re: Almost working pci-arbiter with rumpdisk

2021-02-09 Thread Samuel Thibault
Damien Zammit, le mar. 09 févr. 2021 21:42:29 +1100, a ecrit: > 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 -> > fsys_startup? > As t

Re: Almost working pci-arbiter with rumpdisk

2021-02-09 Thread Damien Zammit
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 th

Re: Almost working pci-arbiter with rumpdisk

2021-02-08 Thread Samuel Thibault
Hello, 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) > In pci-arbiter, what port rights do I return in device_open? T

Almost working pci-arbiter with rumpdisk

2021-02-08 Thread Damien Zammit
Hi, I'm getting very close to working pci + rump. In pci-arbiter, what port rights do I return in device_open? I am currently doing this: static io_return_t device_open (mach_port_t reply_port, mach_msg_type_name_t reply_port_type, dev_mode_t mode, char *name, device_t * devp,