From: Eric Auger <eric.auger@redhat.com>
To: eric.auger.pro@gmail.com, linux-kernel@vger.kernel.org,
mihai.carabas@oracle.com, gregkh@linuxfoundation.org,
andriy.shevchenko@linux.intel.com
Cc: arnd@arndb.de, pizhenwei@bytedance.com, pbonzini@redhat.com,
joe@perches.com, drjones@redhat.com
Subject: Re: [PATCH v2] misc/pvpanic-pci: Allow automatic loading
Date: Thu, 8 Jul 2021 13:58:18 +0200 [thread overview]
Message-ID: <3e006cfb-f965-67b8-7167-dc2fcf342361@redhat.com> (raw)
In-Reply-To: <20210629072214.901004-1-eric.auger@redhat.com>
Hi Greg,
On 6/29/21 9:22 AM, Eric Auger wrote:
> The virtual machine monitor (QEMU) exposes the pvpanic-pci
> device to the guest. On guest side the module exists but
> currently isn't loaded automatically. So the driver fails
> to be probed and does not its job of handling guest panic
> events.
>
> Instead of requiring manual modprobe, let's include a device
> database using the MODULE_DEVICE_TABLE macro and let the
> module auto-load when the guest gets exposed with such a
> pvpanic-pci device.
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
Maybe I misunderstood your question on the v1. This patch does not
result from an issue found by a tool/script but was identified while
exercising the pvpanic-pci use case "manually".
Thanks
Eric
>
> ---
>
> v1 -> v2:
> - enhance the commit message with additional info (Greg, Andy)
> ---
> drivers/misc/pvpanic/pvpanic-pci.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/misc/pvpanic/pvpanic-pci.c b/drivers/misc/pvpanic/pvpanic-pci.c
> index 9ecc4e8559d5d..30290d42d8aa8 100644
> --- a/drivers/misc/pvpanic/pvpanic-pci.c
> +++ b/drivers/misc/pvpanic/pvpanic-pci.c
> @@ -122,4 +122,6 @@ static struct pci_driver pvpanic_pci_driver = {
> },
> };
>
> +MODULE_DEVICE_TABLE(pci, pvpanic_pci_id_tbl);
> +
> module_pci_driver(pvpanic_pci_driver);
prev parent reply other threads:[~2021-07-08 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 7:22 Eric Auger
2021-07-08 11:58 ` Eric Auger [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=3e006cfb-f965-67b8-7167-dc2fcf342361@redhat.com \
--to=eric.auger@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=drjones@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.carabas@oracle.com \
--cc=pbonzini@redhat.com \
--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
all inboxes | Powered by JetHome®