From: zhenwei pi <pizhenwei@bytedance.com>
To: arnd@arndb.de, gregkh@linuxfoundation.org
Cc: pbonzini@redhat.com, linux-kernel@vger.kernel.org,
pizhenwei@bytedance.com
Subject: [PATCH v3 2/2] misc: pvpanic: introduce module parameter 'events'
Date: Fri, 8 Jan 2021 21:52:23 +0800 [thread overview]
Message-ID: <20210108135223.2924507-3-pizhenwei@bytedance.com> (raw)
In-Reply-To: <20210108135223.2924507-1-pizhenwei@bytedance.com>
Suggested by Paolo, add a module parameter that can be used to limit
which capabilities the driver uses.
Finally, the pvpanic guest driver works by the limitation of both
device capability and user setting.
Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
---
drivers/misc/pvpanic.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/misc/pvpanic.c b/drivers/misc/pvpanic.c
index e1023c7b8fb0..417f1086e764 100644
--- a/drivers/misc/pvpanic.c
+++ b/drivers/misc/pvpanic.c
@@ -19,6 +19,10 @@
#include <uapi/misc/pvpanic.h>
static void __iomem *base;
+static unsigned int events = PVPANIC_PANICKED | PVPANIC_CRASH_LOADED;
+module_param(events, uint, 0644);
+MODULE_PARM_DESC(events, "set event limitation of pvpanic device");
+
static unsigned int capability = PVPANIC_PANICKED | PVPANIC_CRASH_LOADED;
static ssize_t capability_show(struct device *dev,
@@ -48,7 +52,7 @@ MODULE_LICENSE("GPL");
static void
pvpanic_send_event(unsigned int event)
{
- if (event & capability)
+ if (event & capability & events)
iowrite8(event, base);
}
--
2.25.1
next prev parent reply other threads:[~2021-01-08 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 13:52 [PATCH v3 0/2] misc: pvpanic: introduce capability & module parameter zhenwei pi
2021-01-08 13:52 ` [PATCH v3 1/2] misc: pvpanic: introduce device capability zhenwei pi
2021-01-08 14:06 ` Greg KH
2021-01-08 13:52 ` zhenwei pi [this message]
2021-01-08 14:07 ` [PATCH v3 2/2] misc: pvpanic: introduce module parameter 'events' Greg KH
2021-01-08 15:04 ` Paolo Bonzini
2021-01-08 15:15 ` Greg KH
2021-01-08 15:26 ` Paolo Bonzini
2021-01-09 11:31 ` Greg KH
2021-01-10 3:10 ` [External] " zhenwei pi
2021-01-11 18:27 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210108135223.2924507-3-pizhenwei@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).