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: Auger Eric <eric.auger@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 3/3] vfio/common: Introduce vfio_set_irq_signaling helper
Date: Tue, 2 Jul 2019 10:30:25 -0600	[thread overview]
Message-ID: <20190702103025.72258b47@x1.home> (raw)
In-Reply-To: <CAFEAcA-KuwMqTdw9Co+KRJTD=gvQ9qwU9QF3xsScLyZzPzaK2A@mail.gmail.com>

On Tue, 2 Jul 2019 16:58:02 +0100
Peter Maydell <peter.maydell@linaro.org> wrote:

> On Tue, 2 Jul 2019 at 16:56, Alex Williamson <alex.williamson@redhat.com> wrote:
> > When we're emulating writes to the MSI-X vector table we have no
> > failure path up to the guest.  Real hardware cannot fail to enable a
> > vector that's available in hardware, thus we can either log the issue,
> > ignore the issue, or fault.  I guess Coverity is simply noting that
> > other cases are tested while this is not, therefore we should either
> > explicitly ignore the return value with a cast to void or take this as
> > an opportunity to log the fault, which might be useful in debugging a
> > device that isn't working properly.  Thanks,  
> 
> Yeah, Coverity's check here is purely a heuristic ("did we seem
> to check returns from this function in other places?") so it's
> wrong sometimes. If you want me to mark this as a false positive
> in the coverity UI I can do that.

TBH, it seems like a good nag to log it properly.  Eric, do you mind
posting a fix to do that?  Thanks,

Alex


  reply	other threads:[~2019-07-02 18:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-13 21:33 [Qemu-devel] [PULL 0/3] vfio updates 2019-06-13 Alex Williamson
2019-06-13 21:33 ` [Qemu-devel] [PULL 1/3] vfio/pci: Hide Resizable BAR capability Alex Williamson
2019-06-13 21:33 ` [Qemu-devel] [PULL 2/3] vfio/pci: Allow MSI-X relocation to fixup bogus PBA Alex Williamson
2019-06-13 21:34 ` [Qemu-devel] [PULL 3/3] vfio/common: Introduce vfio_set_irq_signaling helper Alex Williamson
2019-07-02 10:37   ` Peter Maydell
2019-07-02 12:32     ` Auger Eric
2019-07-02 15:55       ` Alex Williamson
2019-07-02 15:58         ` Peter Maydell
2019-07-02 16:30           ` Alex Williamson [this message]
2019-07-02 16:33             ` Auger Eric
2019-06-14  9:04 ` [Qemu-devel] [PULL 0/3] vfio updates 2019-06-13 Peter Maydell

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=20190702103025.72258b47@x1.home \
    --to=alex.williamson@redhat.com \
    --cc=eric.auger@redhat.com \
    --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).