This would allow pci-arbiter to control which io ports
are accessed and pave the way to having granular access to io ports
based on pci cards exposing their IO BARs.
libpciaccess has convenient api for this kind of access, it allows
opening and registering io ports by BAR.
Therefore, we can first
Hi,
On 22/7/23 21:17, Joan Lledó wrote:
> Correct me if I'm wrong: nested arbiters would fail here, right? An
> arbiter launched from a user (non-root) having permissions over the IO
> file should be able to get the port and handle it to it's clients. Then
> we need the fallback mechanism to RPC t
Hi,
Thank you Damien and Samuel for your explanations.
On 22/7/23 3:31, Damien Zammit wrote:
diff --git a/pci-arbiter/netfs_impl.c b/pci-arbiter/netfs_impl.c
index 4bb5c97a..6b3d6918 100644
--- a/pci-arbiter/netfs_impl.c
+++ b/pci-arbiter/netfs_impl.c
@@ -522,6 +522,14 @@ netfs_attempt_read (st