From: Keir Fraser <keir@xen.org>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: xen-devel@lists.xensource.com,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [xen-4.1-testing test] 9805: regressions - FAIL
Date: Thu, 17 Nov 2011 10:37:01 +0000 [thread overview]
Message-ID: <CAEA944D.343E5%keir@xen.org> (raw)
In-Reply-To: <4EC4E1DD.1030309@canonical.com>
On 17/11/2011 10:28, "Stefan Bader" <stefan.bader@canonical.com> wrote:
>>> Hm, yes we should. I am pretty sure I hit that code path often enough,
>>> Wonder
>>> why I never saw any dead lock there...
>>
>> Perhaps your dom0 kernel doesn't register a pirq_eoi_map.
>>
> Would be the only explanation. And quite possible. Heck, I would need to know
> what that is used for anyway. :/ The kernel is 3.0 based the interrupt I was
> looking at just was a normal apic emulated through events one...
Our automated tests still use 2.6.32. It wouldn't surprise me if upstream
Linux 3 doesn't have the pirq_eoi_map stuff; it's an optimisation rather
than core absolutely-required functionality.
It's the dom0 PV kernel that matters in this case by the way, not the kernel
that you are running in HVM mode as a domU.
-- Keir
next prev parent reply other threads:[~2011-11-17 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 22:23 [xen-4.1-testing test] 9805: regressions - FAIL xen.org
2011-11-17 8:32 ` Jan Beulich
2011-11-17 9:06 ` Keir Fraser
2011-11-17 9:57 ` Stefan Bader
2011-11-17 10:13 ` Keir Fraser
2011-11-17 10:28 ` Stefan Bader
2011-11-17 10:32 ` Stefano Stabellini
2011-11-17 10:37 ` Keir Fraser [this message]
2011-11-17 10:43 ` Stefano Stabellini
2011-11-17 11:32 ` Sander Eikelenboom
2011-11-17 12:42 ` Ian Jackson
2011-11-17 20:03 ` Pasi Kärkkäinen
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=CAEA944D.343E5%keir@xen.org \
--to=keir@xen.org \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=stefan.bader@canonical.com \
--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 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).