Dan Williams
2021-Oct-12 19:13 UTC
[PATCH v5 12/16] PCI: Add pci_iomap_host_shared(), pci_iomap_host_shared_range()
On Tue, Oct 12, 2021 at 11:57 AM Reshetova, Elena <elena.reshetova at intel.com> wrote:> > > > I suspect the true number is even higher because that doesn't include IO > > inside calls to other modules and indirect pointers, correct? > > Actually everything should be included. Smatch has cross-function db and > I am using it for getting the call chains and it follows function pointers. > Also since I am starting from a list of individual read IOs, every single > base read IO in drivers/* should be covered as far as I can see. But if it uses > some weird IO wrappers then the actual list might be higher.Why analyze individual IO calls? I thought the goal here was to disable entire classes of ioremap() users?
Andi Kleen
2021-Oct-12 19:49 UTC
[PATCH v5 12/16] PCI: Add pci_iomap_host_shared(), pci_iomap_host_shared_range()
On 10/12/2021 12:13 PM, Dan Williams wrote:> On Tue, Oct 12, 2021 at 11:57 AM Reshetova, Elena > <elena.reshetova at intel.com> wrote: >> >>> I suspect the true number is even higher because that doesn't include IO >>> inside calls to other modules and indirect pointers, correct? >> Actually everything should be included. Smatch has cross-function db and >> I am using it for getting the call chains and it follows function pointers. >> Also since I am starting from a list of individual read IOs, every single >> base read IO in drivers/* should be covered as far as I can see. But if it uses >> some weird IO wrappers then the actual list might be higher. > Why analyze individual IO calls? I thought the goal here was to > disable entire classes of ioremap() users?This is everything that would need to be moved somewhere else if we didn't disable the entire classes of ioremap users. -Andi