summaryrefslogtreecommitdiff
path: root/lib/raid6/avx2.c
diff options
context:
space:
mode:
authorLogan Gunthorpe <logang@deltatee.com>2019-05-23 16:30:57 -0600
committerJon Mason <jdmason@kudzu.us>2019-06-13 09:02:51 -0400
commita6bed7a541651f5845fba325e311f78c6a4a880a (patch)
treeac1d4bac992fe35b659d70300cd72283ecbe7128 /lib/raid6/avx2.c
parent26b3a37b928457ba2cd98eaf6d7b0feca5a30fa6 (diff)
NTB: Introduce NTB MSI Test Client
Introduce a tool to test NTB MSI interrupts similar to the other NTB test tools. This tool creates a debugfs directory for each NTB device with the following files: port irqX_occurrences peerX/port peerX/count peerX/trigger The 'port' file tells the user the local port number and the 'occurrences' files tell the number of local interrupts that have been received for each interrupt. For each peer, the 'port' file and the 'count' file tell you the peer's port number and number of interrupts respectively. Writing the interrupt number to the 'trigger' file triggers the interrupt handler for the peer which should increment their corresponding 'occurrences' file. The 'ready' file indicates if a peer is ready, writing to this file blocks until it is ready. The module parameter num_irqs can be used to set the number of local interrupts. By default this is 4. This is only limited by the number of unused MSI interrupts registered by the hardware (this will require support of the hardware driver) and there must be at least 2*num_irqs + 1 spads registers available. Signed-off-by: Logan Gunthorpe <logang@deltatee.com> Cc: Dave Jiang <dave.jiang@intel.com> Cc: Allen Hubbe <allenbh@gmail.com> Signed-off-by: Jon Mason <jdmason@kudzu.us>
Diffstat (limited to 'lib/raid6/avx2.c')
0 files changed, 0 insertions, 0 deletions