Date: Wed, 22 Jun 2005 22:37:00 +0930 From: "Wilkinson, Alex" <alex.wilkinson@dsto.defence.gov.au> To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= <des@des.no> Cc: Emanuel Strobl <Emanuel.strobl@gmx.net>, freebsd-current@freebsd.org Subject: Re: lapic@2k interrukts eating CPU cycles Message-ID: <20050622130659.GF63959@squash.dsto.defence.gov.au> In-Reply-To: <86slza27md.fsf@xps.des.no> References: <200506091423.39940@harrymail> <200506211539.26772.jhb@FreeBSD.org> <200506220122.24315@harrymail> <86slza27md.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
0n Wed, Jun 22, 2005 at 09:06:18AM +0200, Dag-Erling Smrgrav wrote:
>Emanuel Strobl <Emanuel.strobl@gmx.net> writes:
>> I don't know what lapic stands for (the l, if apic means
>> AdvancedProgrammableInterruptController)
>
>local, meaning per-CPU as opposed to the IOAPIC which is located in
>the south bridge and shared by all CPUs.
Why do we need both LAPIC *and* an IO-APIC ?
- aW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050622130659.GF63959>