From: Avi Kivity <avi@qumranet.com>
To: david ahern <daahern@cisco.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: still seeing network freezes with rtl8139 nic
Date: Mon, 25 Feb 2008 19:19:57 +0200 [thread overview]
Message-ID: <47C2F8BD.4090504@qumranet.com> (raw)
In-Reply-To: <47C2F57C.9040903@cisco.com>
david ahern wrote:
> david ahern wrote:
>
>> Avi Kivity wrote:
>>
>>> - the in-kernel ioapic is buggy and needs the extra kicking the
>>> optimization prevents. Can be checked by re-adding the optimization to
>>> kvm_ioapic_set_irq() (keeping it removed in qemu). If it works, the
>>> problem is in userspace. If it fails, the problem is in the kernel.
>>>
>>> Something like
>>>
>>> static int old_level[16];
>>>
>>> if (level == old_level[irq])
>>> return;
>>> old_level[irq] = level;
>>>
>>>
>
> With the "if (!change) return;" taken out of pci_set_irq() and the above code
> added to kvm_ioapic_set_irq() networking froze.
>
That points the finger at the kernel ioapic.
I saw from the /proc/interrupts dump that it's an smp guest. Does it
freeze on uniprocessor as well? Maybe it's bad locking in the kernel.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-25 17:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 18:33 still seeing network freezes with rtl8139 nic david ahern
2008-02-24 10:14 ` Avi Kivity
2008-02-24 19:49 ` david ahern
2008-02-25 8:54 ` Avi Kivity
2008-02-25 16:11 ` david ahern
2008-02-25 17:06 ` david ahern
2008-02-25 17:19 ` Avi Kivity [this message]
2008-02-26 4:57 ` david ahern
2008-02-26 9:19 ` Avi Kivity
2008-02-26 14:41 ` Avi Kivity
2008-02-26 14:55 ` david ahern
2008-02-26 14:50 ` david ahern
2008-02-26 15:07 ` Avi Kivity
2008-03-04 18:05 ` Eckersid SIlapaswang
2008-03-05 15:04 ` david ahern
2008-03-05 17:14 ` Avi Kivity
2008-03-05 18:33 ` david ahern
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=47C2F8BD.4090504@qumranet.com \
--to=avi@qumranet.com \
--cc=daahern@cisco.com \
--cc=kvm-devel@lists.sourceforge.net \
/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