From: Paolo Bonzini <pbonzini@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: zhenwei pi <pizhenwei@bytedance.com>,
arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] misc: pvpanic: introduce module parameter 'events'
Date: Mon, 11 Jan 2021 19:27:16 +0100 [thread overview]
Message-ID: <429436d3-ddd7-a1d6-4ed6-1f0932f2150e@redhat.com> (raw)
In-Reply-To: <X/mT/9qKswNUIWTc@kroah.com>
On 09/01/21 12:31, Greg KH wrote:
>> Also considering that there will not be more than one copy of this device
>> (it doesn't make sense as they would all do exactly the same thing), in this
>> case a module parameter really seems to be the simplest way to configure it.
>
> So you never can have more than one of these in the system at one time?
> Because if this ever becomes not true, the module parameter is a mess...
There shouldn't be. The device is only telling the host about
panic-related events in the guest. The multiplexing of events to
multiple interested listeners happens on the other side.
Paolo
prev parent reply other threads:[~2021-01-11 18:28 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 ` [PATCH v3 2/2] misc: pvpanic: introduce module parameter 'events' zhenwei pi
2021-01-08 14:07 ` 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 [this message]
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=429436d3-ddd7-a1d6-4ed6-1f0932f2150e@redhat.com \
--to=pbonzini@redhat.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pizhenwei@bytedance.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).