From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1BUgR3-00044C-Lk
	for qemu-devel@nongnu.org; Mon, 31 May 2004 02:38:14 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1BUgQy-00042r-Oe
	for qemu-devel@nongnu.org; Mon, 31 May 2004 02:38:12 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1BUgQy-00042E-F2
	for qemu-devel@nongnu.org; Mon, 31 May 2004 02:38:08 -0400
Received: from [195.9.147.9] (helo=dionis.simtreas.ru)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1BUgPl-0002bW-9e
	for qemu-devel@nongnu.org; Mon, 31 May 2004 02:36:53 -0400
Message-ID: <40BAD31E.7050807@simtreas.ru>
Date: Mon, 31 May 2004 10:39:26 +0400
From: "Vladimir N. Oleynik" <dzo@simtreas.ru>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: AIO ide patch
References: <40B37520.7020807@simtreas.ru> <40B4AC26.8050002@witch.dyndns.org>
	<40B4A526.10807@simtreas.ru>
	<200405301730.06075.hetz@witch.dyndns.org>
In-Reply-To: <200405301730.06075.hetz@witch.dyndns.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: hetz@witch.dyndns.org
Cc: qemu-devel@nongnu.org

Hetz,

>>I want see Fabrice a reaction. I don`t know of safe my idea.
>>I tested 3-th variant with AIO for ATAPI. My tests is works.
>>
>>
>>ftp://ftp.simtreas.ru/pub/my/qemu/qemu_aio.patch3.gz

> Well, safe  - it's not :(

May be. Qemu have comment for demontsrate this ;-)

/* XXX: tb_flush is currently not thread safe */
....
     if (cpu_single_env)
         env = cpu_single_env; /* XXX: find a correct solution for multithread */

And many other...

Current cpu_single_env=global_env and cpu_loop() have save context by localy,
not to env. io_port make irq from signle_env, mail_loop() make timer irq from
global_env, network fd_read make irq from mail_loop() with single_env...
I confused this. The current design may be ready not thread safe, but have
working progress for this.

> It seems that with your patch, Windows XP upon booting complains about wrong 
> HAL, and doesn't boot. Windows 98 complains about corrupt hard drive and 
> doesn't boot either.

Heh. My WinXP installation with AIO_patch4v is ok.
4v have async call all set_irq with usage sched_yield().

--w
vodz