From: "Vladimir N. Oleynik" <dzo@simtreas.ru>
To: whit74@verbmail.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Windows 2000 disk full problem during install...
Date: Fri, 17 Dec 2004 20:42:47 +0300 [thread overview]
Message-ID: <41C31A97.3010309@simtreas.ru> (raw)
Leo,
>> This correction adds waiting one (or zero, autorandomly) period before
>> sending interruption after positioning before write. (see attach)
>> But this a HACK, do not use after w2k install!
> Can you explain why we shouldn't use this other than for win2k install?
> I'm not too familiar with the IDE emulation and am not sure what the
> consequences would be. Of course, it is easy to disable at run time by
> just setting s->ide_set_irq_from_timer = 0. I am just trying to
> understand more about this - what the real problem seems to be, what the
> danger of using this hack after install is, etc.
The periods of the timer too big.
After that hack the host-system will be all more and to be slowed down
at the reference to fragments files.
> I will investigate your AIO solution as well - do you feel that it is
> more correct than this non-AIO patch?
Yes. But I offered idea which most likely works only for softmmu variant
and may be not works for qemu-fast/usermode.
I can`t test -fast variant and unlike -usermode.
--w
vodz
next reply other threads:[~2004-12-17 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 17:42 Vladimir N. Oleynik [this message]
[not found] <200412142142.iBELg2Qa009126@treas.simtreas.ru>
2004-12-17 11:23 ` [Qemu-devel] Re: Windows 2000 disk full problem during install Vladimir N. Oleynik
2004-12-17 11:51 ` Piotras
2004-12-17 14:15 ` Leo Whitman
2005-04-30 16:18 ` Fabrice Bellard
-- strict thread matches above, loose matches on Subject: below --
2004-12-14 20:58 [Qemu-devel] " Leo Whitman
2004-12-15 6:50 ` [Qemu-devel] " Janusz S. Bień
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=41C31A97.3010309@simtreas.ru \
--to=dzo@simtreas.ru \
--cc=qemu-devel@nongnu.org \
--cc=whit74@verbmail.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).