qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: test_isa_retry_flush() in ide-test.c
Date: Tue, 11 Jan 2022 18:34:20 -0500	[thread overview]
Message-ID: <CAFn=p-Zhab9KT050opxOWbvsBGR3+nx-1Xgm-rEJ11KnvttW4w@mail.gmail.com> (raw)
In-Reply-To: <4e54ef7d-ac0a-e2b2-faee-fddeaeac422b@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]

On Fri, Jan 7, 2022, 12:27 PM Paolo Bonzini <pbonzini@redhat.com> wrote:

> On 1/7/22 17:01, Thomas Huth wrote:
> >   Hi John!
> >
> > I just notice that test_isa_retry_flush() is not doing anything useful
> > anymore: It likely was supposed to run the test_retry_flush() function
> > with the "isapc" machine type, but actually test_retry_flush() ignores
> > the machine option parameter completely and always uses PCI accessor
> > functions nowadays (since commit 9c268f8ae84ae186).
> > Question is: Is it worth the effort to try to restore the original
> > intended behavior for the ISA test here, or shall we rather simply
> > remove it instead to save some testing cycles?
>
> The right way to fix it would be to use qgraph.  Second best option is
> to nuke it, because the conversion to qgraph would give the test back
> for free without writing more code.
>
> Paolo
>
>
Uh, nuke it. I think maybe this never worked correctly ...?

I'm looking at baca2b9e3a94be1690fc4a842a97b64a4c8f892c and it doesn't look
like I ever routed the const char *machine to go anywhere ... ? Maybe it
was a mis-merge or just a thinko, but I think you're safe to just destroy
it...

--js

[-- Attachment #2: Type: text/html, Size: 1726 bytes --]

      reply	other threads:[~2022-01-11 23:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 16:01 test_isa_retry_flush() in ide-test.c Thomas Huth
2022-01-07 17:27 ` Paolo Bonzini
2022-01-11 23:34   ` John Snow [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='CAFn=p-Zhab9KT050opxOWbvsBGR3+nx-1Xgm-rEJ11KnvttW4w@mail.gmail.com' \
    --to=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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;
as well as URLs for NNTP newsgroup(s).