Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: David Matlack <dmatlack@google.com>
To: Josh Hilke <jrhilke@google.com>
Cc: Alex Williamson <alex@shazbot.org>,
	Vipin Sharma <vipinsh@google.com>,
	Jason Gunthorpe <jgg@nvidia.com>, Shuah Khan <shuah@kernel.org>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] vfio: selftests: Add driver for IGB QEMU device
Date: Wed, 13 May 2026 23:33:02 +0000	[thread overview]
Message-ID: <agUKLmKLoV71Hq6S@google.com> (raw)
In-Reply-To: <CAAdrzjuf3z-CyWeBRPKmMQxmQZ9U=2Tc0cDAFqdRFRDHKw_K-Q@mail.gmail.com>

On 2026-05-13 11:49 AM, Josh Hilke wrote:
> On Tue, May 12, 2026 at 7:12 PM Josh Hilke <jrhilke@google.com> wrote:
> > On Mon, May 11, 2026 at 4:45 PM David Matlack <dmatlack@google.com> wrote:
> > > On 2026-05-11 09:18 PM, Josh Hilke wrote:

> > > > +     retries = 100;
> > > > +     while (retries-- > 0) {
> > > > +             if (rx->wb.status_error & 1)
> > > > +                     break;
> > > > +             usleep(10);
> > > > +     }
> > >
> > > Why bail after a certain timeout? The test may have kicked off a large
> > > count of memcpys. Is this for error detection?
> >
> > The bailout was intended to detect errors during development.
> > Shouldn't need it anymore. I'll remove it in v2.
> 
> Sorry, I forgot: we need the timeout  to detect DMA errors for the
> memcpy_from_unmapped_iova test in vfio_pci_driver_test. The test
> triggers an IOMMU fault because the IOVA is unmapped, and the IOMMU
> aborts the DMA operation. However, the QEMU IGB implementation does
> not set an error bit, so timing out is our only method for error
> detection.

Hm... that's going to be tricky then. This means we would have to set
the timeout to longer than the longest possible memcpy duration to avoid
false negatives? That means we'll have to set the timeout to quite long.

  reply	other threads:[~2026-05-13 23:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 21:18 [PATCH] vfio: selftests: Add driver for IGB QEMU device Josh Hilke
2026-05-11 23:45 ` David Matlack
2026-05-13  2:12   ` Josh Hilke
2026-05-13 18:49     ` Josh Hilke
2026-05-13 23:33       ` David Matlack [this message]
2026-05-13 23:29     ` David Matlack

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=agUKLmKLoV71Hq6S@google.com \
    --to=dmatlack@google.com \
    --cc=alex@shazbot.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=jgg@nvidia.com \
    --cc=jrhilke@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=vipinsh@google.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