qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH for-1.3] vfio-pci: Fix KVM disabled path
Date: Fri, 30 Nov 2012 12:14:33 -0700	[thread overview]
Message-ID: <1354302873.1809.246.camel@bling.home> (raw)
In-Reply-To: <CAFEAcA_hr2HLPTWq9pH4wk58mxrnVUjOHe4AXY-pbS0z9FjXAA@mail.gmail.com>

On Fri, 2012-11-30 at 18:57 +0000, Peter Maydell wrote:
> On 27 November 2012 19:45, Alex Williamson <alex.williamson@redhat.com> wrote:
> > kvm_check_extension() explodes when KVM isn't enabled so we need to
> > first test whether KVM is enabled.  Use kvm_irqchip_in_kernel() for
> > this since it matches the test we do before using this result.
> 
> > --- a/hw/vfio_pci.c
> > +++ b/hw/vfio_pci.c
> > @@ -438,7 +438,8 @@ static int vfio_enable_intx(VFIODevice *vdev)
> >       * Only conditional to avoid generating error messages on platforms
> >       * where we won't actually use the result anyway.
> >       */
> > -    if (kvm_check_extension(kvm_state, KVM_CAP_IRQFD_RESAMPLE)) {
> > +    if (kvm_irqchip_in_kernel() &&
> > +        kvm_check_extension(kvm_state, KVM_CAP_IRQFD_RESAMPLE)) {
> >          vdev->intx.route = pci_device_route_intx_to_irq(&vdev->pdev,
> >                                                          vdev->intx.pin);
> 
> 
> vfio_pci is supposed to be architecture-independent code, right?
> kvm.h says you mustn't use kvm_irqchip_in_kernel() in such code
> (its semantics vary from arch to arch). I think kvm_enabled()
> is sufficient here since what we're actually guarding is just
> the kvm_check_extension call.

Here, yes.  The other call spot we're matching is specifically looking
for whether kvm is capable of using IRQFD_RESAMPLE and whether it should
be used.  I think kvm_irqfds_enabled() is probably the right way to go.
Post 1.3 we might want to make kvm_intx_via_irqfd_enabled which
encapsulates the IRQFD_RESAMPLE test.  I'll do some testing and repost a
kvm_irqfds_enabled() version.  Thanks,

Alex

      reply	other threads:[~2012-11-30 19:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27 19:45 [Qemu-devel] [PATCH for-1.3] vfio-pci: Fix KVM disabled path Alex Williamson
2012-11-30 18:57 ` Peter Maydell
2012-11-30 19:14   ` Alex Williamson [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=1354302873.1809.246.camel@bling.home \
    --to=alex.williamson@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).