qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: zitu <zitu@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] enabling bus-master IDE driver
Date: Fri,  5 Nov 2004 14:32:00 +0100	[thread overview]
Message-ID: <1099661520.418b80d07e377@imp5-q.free.fr> (raw)
In-Reply-To: <BAY24-F27Q1WE9ql2Rk000265a2@hotmail.com>

Quoting Simon Frew <thargthedestroyer@hotmail.com>:
> Running qemu with 512mb ram.  Seems to work fine, but guest o/s installation
> was very slow.  So after reading through previous posts on here I found the
> patch posted previously to enable dma for ide, and have applied that to
> ide.c
> and rebuilt qemu.  Then in windows go to device manager and see what it
> thinks
> is installed.  Device manager says I have a Intel 82371SB PCI Bus Master IDE
> controller.  So I right-click on "Primary IDE channel" and look in
> properties->advanced settings.  Transfer Mode is set to "DMA if available"
> and current transfer mode says "PIO mode".  So it still seems to be in PIO
> mode!

I have the same problem inside XP guest too. Linux guest seems really in
DMA mode, since my transfer rates go from 17MB to 47MB on a 512MB hdd image.

>
> Does that mean that the patch doesn't work?  Do I have to do something else
> to make dma work?

I think this patch is almost complete for linux and solaris guests. Some
more work/init is needed inside XP/NT/2K. Anyone around with this
knowledge ?

Zitu
--

  reply	other threads:[~2004-11-05 13:41 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-04 20:35 [Qemu-devel] enabling bus-master IDE driver Simon Frew
2004-11-05 13:32 ` zitu [this message]
2004-11-05 15:02   ` zitu
2004-11-06  1:53     ` Jason Brittain
2004-11-06 14:27       ` Johannes Schindelin
2004-11-06 21:52         ` Jason Brittain
2004-11-07  9:03           ` Jens Axboe
2004-11-07  9:21             ` Jens Axboe
2004-11-07  9:38               ` Jens Axboe
2004-11-07 11:01                 ` Hetz Ben Hamo
2004-11-07 11:16                   ` Jens Axboe
2004-11-08 10:15                     ` zitu
2004-11-08 16:51                       ` Andreas Bollhalder
2004-11-09  7:38                     ` Paul Jakma
2004-11-09 10:28                       ` Hetz Ben Hamo
2004-11-09 13:53                         ` Paul Jakma
2004-11-11 17:29                     ` Jason Brittain
2004-11-11 19:06                       ` Jens Axboe
2004-11-11 19:02                         ` Jason Brittain
2004-11-11 19:16                           ` Jens Axboe
2004-11-12  8:42                             ` Jens Axboe
2004-11-07 11:02             ` James Boddington
2004-11-10  1:41             ` James Boddington
2004-11-06 21:57         ` James Boddington
2004-11-06 22:11           ` James Boddington
2004-11-06 23:46             ` zitu
2004-11-07  0:41               ` jeebs
2004-11-07  7:12               ` Jason Brittain
  -- strict thread matches above, loose matches on Subject: below --
2004-11-05 15:37 Juergen Keil
2004-11-05 15:43 ` zitu
2004-11-05 15:45 ` zitu
2004-11-05 15:52   ` Jens Axboe
2004-11-05 16:10     ` zitu
2004-11-05 17:30       ` Damien Mascord
2004-11-12 14:27 Juergen Keil
2004-11-12 18:02 ` Jason Brittain
2004-11-12 19:07 Juergen Keil
2004-11-16 19:41 ` Juergen Lock
2004-11-23  5:12   ` Norikatsu Shigemura
2004-11-25 21:12     ` Juergen Lock
2004-11-26 10:48 Juergen Keil
2004-11-28 20:09 ` Juergen Lock

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=1099661520.418b80d07e377@imp5-q.free.fr \
    --to=zitu@free.fr \
    --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).