From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Lin, Ray" <Ray.Lin@lsi.com>
Cc: "jeremy@goop.org" <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"keir@xen.org" <keir@xen.org>,
"bruce.edge@gmail.com" <bruce.edge@gmail.com>,
"Ian.Campbell@eu.citrix.com" <Ian.Campbell@eu.citrix.com>,
"linux@eikelenboom.it" <linux@eikelenboom.it>,
"m.a.young@durham.ac.uk" <m.a.young@durham.ac.uk>
Subject: Re: FW: Xen 4.1 interrupts not delievered.
Date: Mon, 18 Oct 2010 10:59:24 -0400 [thread overview]
Message-ID: <20101018145924.GA27373@dumpdata.com> (raw)
In-Reply-To: <EB4C61A1A2501842A04B573FE42B14D601319D0DDD@cosmail02.lsi.com>
On Fri, Oct 15, 2010 at 02:57:44PM -0600, Lin, Ray wrote:
>
> We experienced the domU interrupt/DMA issue before. The symptom is like the /proc/interrupts/irq# of Tachyon chip (FC controller) keep on incrementing, but nobody is serving the interrupts. Eventually the count of these unserved interrupts reach the max. and are forced to be disabled. With Konrad's dom0/domU configuration, this issue is resolved now.
Can you send the old dom0/domU configuration? I am really curious
as of why it would work - the configuration for domU was just
mostly made minimal to boot a tiny kernel, and the dom0
was based on Ubuntu/Fedora Core 13 and then enabling all of the
Xen options.
next prev parent reply other threads:[~2010-10-18 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 20:57 FW: Xen 4.1 interrupts not delievered Lin, Ray
2010-10-18 14:59 ` Konrad Rzeszutek Wilk [this message]
2010-10-18 15:18 ` Lin, Ray
2010-10-18 16:12 ` Bruce Edge
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=20101018145924.GA27373@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ray.Lin@lsi.com \
--cc=bruce.edge@gmail.com \
--cc=jeremy@goop.org \
--cc=keir@xen.org \
--cc=linux@eikelenboom.it \
--cc=m.a.young@durham.ac.uk \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.