From: linas@austin.ibm.com (Linas Vepstas)
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, Nathan Lynch <ntl@pobox.com>
Subject: Re: Hard hang in hypervisor!?
Date: Thu, 11 Oct 2007 15:30:21 -0500 [thread overview]
Message-ID: <20071011203021.GC4258@austin.ibm.com> (raw)
In-Reply-To: <18189.26776.326248.278431@cargo.ozlabs.ibm.com>
On Thu, Oct 11, 2007 at 10:04:40AM +1000, Paul Mackerras wrote:
> Linas Vepstas writes:
>
> > Err .. it was cpu 0 that was spinlocked. Are interrupts not
> > distributed?
>
> We have some bogosities in the xics code that I noticed a couple of
> days ago. Basically we only set the xics to distribute interrupts to
> all cpus if (a) the affinity mask is equal to CPU_MASK_ALL (which has
> ones in every bit position from 0 to NR_CPUS-1) and (b) all present
> cpus are online (cpu_online_map == cpu_present_map). Otherwise we
> direct interrupts to the first cpu in the affinity map. So you can
> easily have the affinity mask containing all the online cpus and still
> not get distributed interrupts.
>
> So in your case it's quite possible that all interrupts were directed
> to cpu 0.
Thanks,
I'll give this a whirl if I don't get distracted by other tasks.
A simple cat /proc/interrupts shows them evenly distributed on
my "usual" box, and all glommed up on cpu 0 on the one thats
giving me fits.
Also, I noticed years ago that "BAD" was non-zero and large.
Vowed to look into it someday ...
--linas
next prev parent reply other threads:[~2007-10-11 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 20:37 Hard hang in hypervisor!? Linas Vepstas
2007-10-09 21:18 ` Nathan Lynch
2007-10-09 21:28 ` Linas Vepstas
2007-10-09 23:22 ` never mind .. [was " Linas Vepstas
2007-10-11 0:04 ` Paul Mackerras
2007-10-11 20:30 ` Linas Vepstas [this message]
2007-10-11 21:35 ` Milton Miller
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=20071011203021.GC4258@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
--cc=paulus@samba.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).