From: Alex Williamson <alex.williamson@redhat.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, feng.wu@intel.com,
linux-kernel@vger.kernel.org, eric.auger@linaro.org
Subject: [PATCH 0/2] irqbypass/kvm: Silence registration errors
Date: Thu, 05 May 2016 11:58:23 -0600 [thread overview]
Message-ID: <20160505174733.9576.61083.stgit@gimli.home> (raw)
Currently an AMD system using vfio-pci/kvm will issue a dev_info() for
every MSI/X vector registered because kvm_x86_ops does not support a
bypass mechanism except on Intel and the add_producer callback returns
an errno for that. This is meaningless, unintended, and confuses
users. We could simply have KVM's add_producer callback return 0 if
there's no bypass mechanism, but then why are we registering as an IRQ
bypass consumer in the first place? We also don't necessarily want to
simply remove the dev_info/pr_info on registration failure because
then we have no warning if something does actually go wrong. So
instead, let's conditionalize IRQ bypass registration on whether we
have any support for it, and to keep the de-registration path clean
and fill an unintended gap, let's ignore deregistration of NULL tokens
and prevent registration of the same. NULL isn't a good, unique
cookie anyway. Tested on AMD and non-PI Intel. Thanks,
Alex
---
Alex Williamson (2):
irqbypass: Disallow NULL token
kvm: Conditionally register IRQ bypass consumer
arch/x86/kvm/x86.c | 19 ++++++++-----------
include/linux/irqbypass.h | 4 ++--
include/linux/kvm_host.h | 1 +
virt/kvm/eventfd.c | 18 ++++++++++--------
virt/lib/irqbypass.c | 12 +++++++++++-
5 files changed, 32 insertions(+), 22 deletions(-)
next reply other threads:[~2016-05-05 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 17:58 Alex Williamson [this message]
2016-05-05 17:58 ` [PATCH 1/2] irqbypass: Disallow NULL token Alex Williamson
2016-05-05 17:58 ` [PATCH 2/2] kvm: Conditionally register IRQ bypass consumer Alex Williamson
2016-05-11 14:49 ` [PATCH 0/2] irqbypass/kvm: Silence registration errors 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=20160505174733.9576.61083.stgit@gimli.home \
--to=alex.williamson@redhat.com \
--cc=eric.auger@linaro.org \
--cc=feng.wu@intel.com \
--cc=kvm@vger.kernel.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
all inboxes | Powered by JetHome®