search for: map_nam

...of/base.c b/drivers/of/base.c index 09692c9b32a7..99f6bfa9b898 100644 --- a/drivers/of/base.c +++ b/drivers/of/base.c @@ -2237,8 +2237,12 @@ int of_map_rid(struct device_node *np, u32 rid, return 0; } - pr_err("%pOF: Invalid %s translation - no match for rid 0x%x on %pOF\n", - np, map_name, rid, target && *target ? *target : NULL); - return -EFAULT; + pr_info("%pOF: no %s translation for rid 0x%x on %pOF\n", np, map_name, + rid, target && *target ? *target : NULL); + + /* Bypasses translation */ + if (id_out) + *id_out = rid; + return 0; } EXPORT_SYMBOL...

...--- a/drivers/pci/of.c > > +++ b/drivers/pci/of.c > > @@ -451,9 +451,10 @@ int of_pci_map_rid(struct device_node *np, u32 rid, > > return 0; > > } > > > > - pr_err("%pOF: Invalid %s translation - no match for rid 0x%x on %pOF\n", > > - np, map_name, rid, target && *target ? *target : NULL); > > - return -EFAULT; > > + /* Bypasses translation */ > > + if (id_out) > > + *id_out = rid; > > + return 0; > > } > > > > #if IS_ENABLED(CONFIG_OF_IRQ) > > -- > > 2.19.1 > >

...what is the key to be used, and how the lookup/match happens? and how the mount operations happens? Thanks a lot. I've attached my configuration files below: $ cat /etc/amd.conf ... auto_dir = /.amd_mnt ... map_type = file search_path = /etc ... [ /home ] map_name = amd.home ... $ cat /etc/amd.home /defaults type:=nfs;sublink:=${key};opts:=rw,intr,tcp,nfsvers=3,vers=3,nosuid,nodev,noresvport,rsize=16384,wsize=16384;fs:=${autodir}/${rhost}${rfs} dumbboy rhost:=home111;rfs:=/0/export/home * rhost:=home110;rfs:=/0/export/home ... Thanks.

...gt; --- a/drivers/pci/of.c >> +++ b/drivers/pci/of.c >> @@ -451,9 +451,10 @@ int of_pci_map_rid(struct device_node *np, u32 rid, >> return 0; >> } >> >> - pr_err("%pOF: Invalid %s translation - no match for rid 0x%x on %pOF\n", >> - np, map_name, rid, target && *target ? *target : NULL); >> - return -EFAULT; >> + /* Bypasses translation */ >> + if (id_out) >> + *id_out = rid; >> + return 0; >> } >> >> #if IS_ENABLED(CONFIG_OF_IRQ) >> -- >> 2.19.1 >> > __...

Implement the virtio-iommu driver, following specification v0.9 [1]. Only minor changes since v5 [2]. I fixed issues reported by Michael and added tags from Eric and Bharat. Thanks! You can find Linux driver and kvmtool device on v0.9 branches [3], module and x86 support on virtio-iommu/devel. Also tested with Eric's QEMU device [4]. [1] Virtio-iommu specification v0.9, sources and pdf

Implement the virtio-iommu driver, following specification v0.9 [1]. Only minor changes since v5 [2]. I fixed issues reported by Michael and added tags from Eric and Bharat. Thanks! You can find Linux driver and kvmtool device on v0.9 branches [3], module and x86 support on virtio-iommu/devel. Also tested with Eric's QEMU device [4]. [1] Virtio-iommu specification v0.9, sources and pdf

Implement the virtio-iommu driver, following specification v0.8 [1]. Changes since v2 [2]: * Patches 2-4 allow virtio-iommu to use the PCI transport, since QEMU would like to phase out the MMIO transport. This produces a complex topology where the programming interface of the IOMMU could appear lower than the endpoints that it translates. It's not unheard of (e.g. AMD IOMMU), and the

Implement the virtio-iommu driver, following specification v0.8 [1]. Changes since v2 [2]: * Patches 2-4 allow virtio-iommu to use the PCI transport, since QEMU would like to phase out the MMIO transport. This produces a complex topology where the programming interface of the IOMMU could appear lower than the endpoints that it translates. It's not unheard of (e.g. AMD IOMMU), and the

Implement the virtio-iommu driver, following specification v0.12 [1]. Since last version [2] we've worked on improving the specification, which resulted in the following changes to the interface: * Remove the EXEC flag. * Add feature bit for the MMIO flag. * Change domain_bits to domain_range. Given that there were small changes to patch 5/7, I removed the review and test tags. Please find

Implement the virtio-iommu driver, following specification v0.8 [1]. Changes since v3 [2]: * Rebase onto v4.20-rc2. Patch 3 now touches drivers/of/base.c instead of drivers/pci/of.c, since the map_rid() function has moved. * Removed the request timeout, that depended on DEBUG. * Other small fixes addressing comments on v3. You can find Linux driver and kvmtool device on my virtio-iommu/v0.8.1

Implement the virtio-iommu driver, following specification v0.9 [1]. Since v4 [2] I fixed the issues reported by Eric, and added Reviewed-by from Eric and Rob. Thanks! I changed the specification to fix one inconsistency discussed in v4. That the device fills the probe buffer with zeroes is now a "SHOULD" instead of a "MAY", since it's the only way for the driver to know

Implement the virtio-iommu driver, following specification v0.9 [1]. Since v4 [2] I fixed the issues reported by Eric, and added Reviewed-by from Eric and Rob. Thanks! I changed the specification to fix one inconsistency discussed in v4. That the device fills the probe buffer with zeroes is now a "SHOULD" instead of a "MAY", since it's the only way for the driver to know