From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MoyaJ-0007uW-GM
	for qemu-devel@nongnu.org; Sat, 19 Sep 2009 07:58:35 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MoyaF-0007u3-3U
	for qemu-devel@nongnu.org; Sat, 19 Sep 2009 07:58:35 -0400
Received: from [199.232.76.173] (port=56971 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MoyaE-0007u0-RU
	for qemu-devel@nongnu.org; Sat, 19 Sep 2009 07:58:30 -0400
Received: from moutng.kundenserver.de ([212.227.17.8]:54057)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <weil@mail.berlios.de>) id 1MoyaE-00073d-3G
	for qemu-devel@nongnu.org; Sat, 19 Sep 2009 07:58:30 -0400
Message-ID: <4AB4C761.5030909@mail.berlios.de>
Date: Sat, 19 Sep 2009 13:58:25 +0200
From: Stefan Weil <weil@mail.berlios.de>
MIME-Version: 1.0
References: <BEE650D2F88D74448AD3E613B0C6D4E501091BD9D4@STS-PRG-EXM1M1.sts.sitronics.com>
	<4AB4BD2B.4090809@web.de>
In-Reply-To: <4AB4BD2B.4090809@web.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: eepro100.c
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: Jan Kiszka <jan.kiszka@web.de>
Cc: Michal Filka <mfilka@sitronics.com>, qemu-devel <qemu-devel@nongnu.org>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>

Jan Kiszka schrieb:
> Michal Filka wrote:
>> Hi,
>>
>> I have question on i82557b emulation in kvm.
>>
>> I have run a proprietary operating system (Pharlap OS) in kvm. Part
>> of the job has been porting driver for i8255x. During the job I
>> discovered that kvm's emulation doesn't support a RNR interrupt (it
>> is disabled in the code).
>>
>> Why is it disabled? I'm running heavily loaded application and I have
>> to poll descriptor list instead of waiting for RNR interrupt.
>
> Best asked on qemu-devel, CC'ing the developer of this device model.
>
> Jan
>

Hi,

up to now, nobody complained about the missing RNR interrupts.
Linux obviously works without them, so I had no reason to
implement them.

The disabled code parts (function eepro100_rnr_interrupt)
can be enabled, but you still need code which calls them
at the right places.

This should not be very difficult if there is some test case
which proves the working RNR interrupt.

Regards
Stefan