RE: [Fault-injection-developer] [RFC][PATCH] PCI configuration interceptor patch (ficl, fsml)

[Wang, S. <sta...@in...>]

There is another way to capture the pci configuration access indeed.
We can capture the sequential access to 0xcf8 and 0xcfc instead of place
a probe in the kernel.
You can get the example @ http://easynews.dl.sourceforge.net/sourceforge/fault-injection/mock_e100.tgz

Best Regards,
Stan

> -----Original Message-----
> From: Fumitake ABE [mailto:ab...@jp...]
> Sent: 2003-04-10 17:28
> To: fau...@li...
> Subject: [Fault-injection-developer] [RFC][PATCH] PCI 
> configuration interceptor patch (ficl, fsml)
> 
> 
> Dear All:
> 
> This mail appends two files: a test faultset file (pcitest.fsml) and 
> a patch to ficl implementing a function to use a pci configuration 
> access interceptor (ficl_pci.patch).
> 
> Pci configuration access interceptor can be used by the following:
> 1. apply patches to kernel and ficl
> 2. install the kernel, modules and ficl
> 3. attach kprobe to a pci configuration access 
>    (ficl -p /boot/System.map,/usr/src/linux/vmlinux)
> 4. add a trigger (ficl -i pcitest.fsml)
> 5. access a pci configuration register (e.g. lspci -xx)
> 
> Ficl needs a System.map path and a unzipped kernel file path for 
> attaching kprobe to a pci configuration interceptor. I think that it 
> may be ugly, but I couldn't come up with a better idea than it.
> Please comment.
> 
> Sincerely,
> 
> Fumitake ABE
> ab...@jp...
>