Hi, Greg
What's the next step I should take?
On 1/10/21 7:53 PM, zhenwei pi wrote:
v4 -> v5:
Use sysfs_emit to export attribute value.
Only allow subset of capability to set on events.
Add more detailed infomation in document.
v3 -> v4:
Use event sysfs attribute instead of module parameter.
Use driver dev_groups instead of creating files by sysfs_* API.
v2 -> v3:
Seperate the function to 2 parts:
1, use sysfs to expose device capability.
2, add a module parameter to set limitation by user.
v1 -> v2:
Remove device info log, use module parameter to expose capability.
v1:
The guest sides determines pvpanic capability by RDPT, before kicking
host side, check the event is supported or not.
zhenwei pi (2):
misc: pvpanic: introduce device capability
misc: pvpanic: introduce module parameter 'events'
.../ABI/testing/sysfs-bus-pci-devices-pvpanic | 14 +++++
drivers/misc/pvpanic.c | 58 +++++++++++++++++--
2 files changed, 67 insertions(+), 5 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-bus-pci-devices-pvpanic
--
zhenwei pi
