All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: aliguori@amazon.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PULL 4/5] vfio-pci: Add debug config options to disable MSI/X KVM support
Date: Mon, 09 Dec 2013 10:48:59 +0100	[thread overview]
Message-ID: <52A5920B.2040601@redhat.com> (raw)
In-Reply-To: <1386369360.25738.523.camel@ul30vt.home>

Il 06/12/2013 23:36, Alex Williamson ha scritto:
>>> > >  #define VFIO_ALLOW_MMAP 1
>>> > >  #define VFIO_ALLOW_KVM_INTX 1
>>> > > +#define VFIO_ALLOW_KVM_MSI 1
>>> > > +#define VFIO_ALLOW_KVM_MSIX 1
>> > 
>> > Why not make these device properties instead?
> Honestly, I don't think they're that useful to the average or even to
> the advanced user.  Each of these disables an acceleration/bypass path
> and gives more logging output when debug is enabled.  Otherwise we don't
> get debugging to see when mmap'd BARs are accessed and we can't tell
> when interrupts happen relative to other accesses.  For instance it was
> pretty obvious to find the Nvidia MSI ACK when seeing a config space
> write immediately following an MSI injection.  Without debugging
> enabled, these just slow things down and I don't know of any cases where
> a device behaves better with these features disabled.

Yeah, behaving better is unlikely.  I was thinking of them as a
debugging features.

As to debug messages, have you considered replacing them with tracepoints?

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, aliguori@amazon.com, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PULL 4/5] vfio-pci: Add debug config options to disable MSI/X KVM support
Date: Mon, 09 Dec 2013 10:48:59 +0100	[thread overview]
Message-ID: <52A5920B.2040601@redhat.com> (raw)
In-Reply-To: <1386369360.25738.523.camel@ul30vt.home>

Il 06/12/2013 23:36, Alex Williamson ha scritto:
>>> > >  #define VFIO_ALLOW_MMAP 1
>>> > >  #define VFIO_ALLOW_KVM_INTX 1
>>> > > +#define VFIO_ALLOW_KVM_MSI 1
>>> > > +#define VFIO_ALLOW_KVM_MSIX 1
>> > 
>> > Why not make these device properties instead?
> Honestly, I don't think they're that useful to the average or even to
> the advanced user.  Each of these disables an acceleration/bypass path
> and gives more logging output when debug is enabled.  Otherwise we don't
> get debugging to see when mmap'd BARs are accessed and we can't tell
> when interrupts happen relative to other accesses.  For instance it was
> pretty obvious to find the Nvidia MSI ACK when seeing a config space
> write immediately following an MSI injection.  Without debugging
> enabled, these just slow things down and I don't know of any cases where
> a device behaves better with these features disabled.

Yeah, behaving better is unlikely.  I was thinking of them as a
debugging features.

As to debug messages, have you considered replacing them with tracepoints?

Paolo

  reply	other threads:[~2013-12-09  9:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06 20:48 [PULL 0/5] vfio-pci updates for QEMU 2.0 Alex Williamson
2013-12-06 20:48 ` [Qemu-devel] " Alex Williamson
2013-12-06 20:48 ` [PULL 1/5] linux-headers: Update from v3.13-rc3 Alex Williamson
2013-12-06 20:48   ` [Qemu-devel] " Alex Williamson
2013-12-11 11:09   ` Greg Kurz
2013-12-11 13:15     ` [Qemu-devel] [PATCH] target-ppc: add stubs for KVM breakpoints Greg Kurz
2013-12-11 13:20       ` Alexander Graf
2013-12-11 14:44     ` [Qemu-devel] [PULL 1/5] linux-headers: Update from v3.13-rc3 Alex Williamson
2013-12-11 14:49       ` Alexander Graf
2013-12-06 20:48 ` [PULL 2/5] vfio-pci: Make use of new KVM-VFIO device Alex Williamson
2013-12-06 20:48   ` [Qemu-devel] " Alex Williamson
2013-12-06 20:48 ` [PULL 3/5] vfio-pci: Fix Nvidia MSI ACK through 0x88000 quirk Alex Williamson
2013-12-06 20:48   ` [Qemu-devel] " Alex Williamson
2013-12-06 20:48 ` [PULL 4/5] vfio-pci: Add debug config options to disable MSI/X KVM support Alex Williamson
2013-12-06 20:48   ` [Qemu-devel] " Alex Williamson
2013-12-06 22:06   ` Paolo Bonzini
2013-12-06 22:06     ` [Qemu-devel] " Paolo Bonzini
2013-12-06 22:36     ` Alex Williamson
2013-12-06 22:36       ` [Qemu-devel] " Alex Williamson
2013-12-09  9:48       ` Paolo Bonzini [this message]
2013-12-09  9:48         ` Paolo Bonzini
2013-12-06 20:48 ` [PULL 5/5] vfio-pci: Release all MSI-X vectors when disabled Alex Williamson
2013-12-06 20:48   ` [Qemu-devel] " Alex Williamson

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=52A5920B.2040601@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=aliguori@amazon.com \
    --cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.