From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: jsnow@redhat.com, mark.cave-ayland@ilande.co.uk,
qemu-devel@nongnu.org, atar4qemu@gmail.com, jasper.lowell@bt.com
Subject: Re: Emulating Solaris 10 on SPARC64 sun4u
Date: Fri, 21 Feb 2020 19:53:31 +0000 [thread overview]
Message-ID: <20200221195331.GN2931@work-vm> (raw)
In-Reply-To: <alpine.BSF.2.22.395.2002192059340.88848@zero.eik.bme.hu>
* BALATON Zoltan (balaton@eik.bme.hu) wrote:
> On Wed, 19 Feb 2020, BALATON Zoltan wrote:
> > faster or doing something differently? Does someone know what interrupts
> > are generated on real hardware in DMA mode so we can compare that to
> > what we see with QEMU?
>
> The document Programming Interface for Bus Master IDE Controller, Revision
> 1.0 (5/16/94) has some info on this. AFAIU it says that after DMA operation
> is completed an IRQ should be raised. On page 5, section 3.1. Data
> Synchronization it says:
>
> "Another way to view this requirement is that the first read to the
> controller Status register in response to the IDE device interrupt must
> return with the Interrupt bit set and with the guarantee that all buffered
> data has been written to memory."
>
> Not sure if this is relevant but how is it handled in QEMU? Is the right
> interrupt bit set after DMA transfer is done? If so is it the one that's
> checked by the OS driver?
One thing to be a little careful of is I remember the 646 was always
known for having a few quirks (I've not got a SPARC64 ith one, but I
think my Alpha has it). So whether you're chasing a generic IDE BM
problem or a 646 special is fun.
Dave
> Regards,
> BALATON Zoltan
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-02-21 19:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 6:31 Emulating Solaris 10 on SPARC64 sun4u jasper.lowell
2020-02-05 17:33 ` Dr. David Alan Gilbert
2020-02-07 5:43 ` jasper.lowell
2020-02-08 0:03 ` BALATON Zoltan
2020-02-10 15:38 ` BALATON Zoltan
2020-02-10 19:04 ` John Snow
2020-02-10 22:32 ` Missing IRQ with bmdma on ppc/mips/sparc? (was: Re: Emulating Solaris 10 on SPARC64 sun4u) BALATON Zoltan
2020-02-25 20:55 ` IDE IRQ problem after UDMA enabled " BALATON Zoltan
2020-02-25 22:00 ` BALATON Zoltan
2020-02-25 22:12 ` Emulating Solaris 10 on SPARC64 sun4u BALATON Zoltan
2020-02-09 11:26 ` Mark Cave-Ayland
2020-02-19 3:42 ` jasper.lowell
2020-02-19 18:54 ` BALATON Zoltan
2020-02-19 20:10 ` BALATON Zoltan
2020-02-21 19:53 ` Dr. David Alan Gilbert [this message]
2020-02-28 22:05 ` BALATON Zoltan
2020-03-01 0:15 ` BALATON Zoltan
2020-05-07 14:29 ` jasper.lowell
2020-05-07 15:02 ` Artyom Tarasenko
2020-05-08 2:33 ` jasper.lowell
2020-05-08 8:51 ` Peter Tribble
2020-05-08 13:45 ` Artyom Tarasenko
2020-05-10 2:46 ` jasper.lowell
2020-05-10 9:22 ` Mark Cave-Ayland
2020-05-17 7:57 ` jasper.lowell
2020-05-17 12:37 ` Artyom Tarasenko
2020-05-18 2:56 ` jasper.lowell
2020-05-20 17:44 ` Mike Russo
2020-05-07 18:54 ` BALATON Zoltan
2020-05-08 2:55 ` jasper.lowell
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=20200221195331.GN2931@work-vm \
--to=dgilbert@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=balaton@eik.bme.hu \
--cc=jasper.lowell@bt.com \
--cc=jsnow@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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).