From: Stefan Weil <weil@mail.berlios.de>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Michal Filka <mfilka@sitronics.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: eepro100.c
Date: Sat, 19 Sep 2009 13:58:25 +0200 [thread overview]
Message-ID: <4AB4C761.5030909@mail.berlios.de> (raw)
In-Reply-To: <4AB4BD2B.4090809@web.de>
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
next prev parent reply other threads:[~2009-09-19 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 8:34 eepro100.c Michal Filka
2009-09-19 11:14 ` eepro100.c Jan Kiszka
2009-09-19 11:58 ` Stefan Weil [this message]
2009-09-19 17:10 ` eepro100.c Stefan Weil
2009-09-22 4:50 ` eepro100.c Michal Filka
2009-09-22 9:25 ` eepro100.c Michal Filka
2009-09-22 11:31 ` eepro100.c Michal Filka
2009-09-22 11:56 ` eepro100.c Amit Shah
2009-09-22 16:15 ` eepro100.c Stefan Weil
2009-09-23 5:34 ` eepro100.c Michal Filka
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=4AB4C761.5030909@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mfilka@sitronics.com \
--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).