From: cerise@armory.com
To: linux-smp@vger.kernel.org
Subject: Re: LAPCI disabled for second Processor in 2.6.8-11-amd64-k8-smp kernel - need help reading source code
Date: Thu, 29 Dec 2005 06:53:20 -0800 [thread overview]
Message-ID: <20051229145320.GA5882@boogeyman> (raw)
In-Reply-To: <b713df2c0512280711o7f2b3afo8784d8f5ba12f79f@mail.gmail.com>
On Wed, Dec 28, 2005 at 08:41:19PM +0530, Siju George wrote:
> What is LAPIC?
LAPIC is the Local Advanced Programmable Interrupt Control. In short, it
maps interrupts from the rest of the system to interrupt lines to the processor.
One reason it's programmable rather than a direct line is so that various
interrupts can be multiplexed and one can use the same line for, say, any
PCI device and the PCI bus will sort out which one the CPU should be talking
to.
> Why is it disabled for the second processor?
> Is it normal beavior?
> From lines 121-127 I find this.
>
> -----------------------------
> case ACPI_MADT_LAPIC:
> {
> struct acpi_table_lapic *p =
> (struct acpi_table_lapic*) header;
> printk(KERN_INFO PREFIX "LAPIC (acpi_id[0x%02x]
> lapic_id[0x%02x] %s)\n",
> p->acpi_id, p->id,
> p->flags.enabled?"enabled":"disabled");
> }
> ----------------------------------
> Could some one who works on the kernel or who knows C please interpret
> this for me?
In short, this says that if p->flags.enabled is non-zero, then the LAPIC
is enabled.
I can't find where p->flags.enabled is actually set (though I'll admit that
I didn't look very hard). I suspect that it's read out of the CPU info and
your board is choosing to disable it rather than Linux.
-Phil/CERisE
prev parent reply other threads:[~2005-12-29 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b713df2c0512200246p32b5bad7nc9668fbd955a332b@mail.gmail.com>
2005-12-28 15:11 ` LAPCI disabled for second Processor in 2.6.8-11-amd64-k8-smp kernel - need help reading source code Siju George
2005-12-29 14:53 ` cerise [this message]
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=20051229145320.GA5882@boogeyman \
--to=cerise@armory.com \
--cc=linux-smp@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).