From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: John Snow <jsnow@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Benjamin David Lunt <fys@fysnet.net>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1608802] [NEW] READ_DMA (0xC8) command does not work correctly
Date: Tue, 2 Aug 2016 15:39:08 +0200 [thread overview]
Message-ID: <20160802133908.GA5421@noname.redhat.com> (raw)
In-Reply-To: <c2534862-290f-38a4-384f-21fc9df93cf5@weilnetz.de>
Am 02.08.2016 um 08:52 hat Stefan Weil geschrieben:
> Am 02.08.2016 um 08:11 schrieb Stefan Weil:
> > Public bug reported:
> >
> > The QEMU PC emulation of DMA does not behave like real hardware or other
> > virtualization software.
> >
> > >From the original bug report (Benjamin David Lunt):
> >
> > Back to the READ_DMA command, it is my conclusion that the
> > READ_DMA command, more precisely, the BUS Master part of QEMU is
> > in error. The tests that people have done to see if it works, is
> > probably the guest finding out that DMA doesn't work and defaulting
> > to PIO, but since the read was successful visually to the user, the
> > user assumed the READ_DMA command works, where the guest actually
> > defaulted back to PIO transfers without notice.
> >
> > My code works on real hardware (numerous machines), Bochs, and Oracle's
> > Virtual Box.
> >
> > ...
> >
> > I have a small test suite, zipped and included at:
> > www.fysnet.net/temp/c8bug.zip
> >
> > Within this zip file is a.img. This is a freeDOS bootable
> > floppy. Emulate it with QEMU and then at the DOS prompt, run
> > c8bug.exe.
>
> Hi John,
>
> I got this bug report only recently from a Windows user,
> but it also occurs on Linux.
>
> As I don't know whether this is a regression or whether
> it is relevant for QEMU 2.7, it would be good if you and
> maybe more people could have a look on that problem,
> too.
I don't think it's a regression. I commented with more detail in the bug
report, and despite the test case being buggy it seems to be true that
qemu doesn't get the flags completely right (we should set either BSY or
DRQ, but we do set both). Apparently none of the common drivers check
for this, though, so it never made any difference.
Kevin
next prev parent reply other threads:[~2016-08-02 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 6:11 [Qemu-devel] [Bug 1608802] [NEW] READ_DMA (0xC8) command does not work correctly Stefan Weil
2016-08-02 6:52 ` Stefan Weil
2016-08-02 13:39 ` Kevin Wolf [this message]
2016-08-02 18:09 ` Benjamin David Lunt
2016-08-02 13:30 ` [Qemu-devel] [Bug 1608802] " Kevin Wolf
2020-11-18 10:26 ` Thomas Huth
2021-01-18 4:17 ` Launchpad Bug Tracker
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=20160802133908.GA5421@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=fys@fysnet.net \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).