From: Yinghai Lu <yinghai.lu@amd.com>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org, linuxbios@openbios.org
Subject: Re: x86_64: calibrate_delay_direct and apic id lift for BSP
Date: Fri, 28 Oct 2005 13:19:45 -0700 [thread overview]
Message-ID: <86802c440510281319y667427fj38ffd7a37b8cb77b@mail.gmail.com> (raw)
In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A4201E061EC@ssvlexmb2.amd.com>
I wonder if 8111 only support 4 bit apicid, so it can not send irq to
BSP at apic id 0x10....
YH
On 10/28/05, Lu, Yinghai <yinghai.lu@amd.com> wrote:
> I have tried latest code..., except that, it works well.
>
> YH
>
> -----Original Message-----
> From: Andi Kleen [mailto:ak@suse.de]
> Sent: Friday, October 28, 2005 11:53 AM
> To: Lu, Yinghai
> Cc: discuss@x86-64.org; linux-kernel@vger.kernel.org;
> linuxbios@openbios.org
> Subject: Re: x86_64: calibrate_delay_direct and apic id lift for BSP
>
> On Friday 28 October 2005 20:42, Yinghai Lu wrote:
> > andi,
> >
> > I tried to lift apic id in LinuxBIOS for all cpus after 0x10.
> >
> > When using MB with AMD8111, the jiffies was not moving. So it is
> > locked at calibrate_delay_direct...
>
> Have you tried it with 2.6.14? It has some new code to handle
> high apic ids better
>
> > but MB with Nvidia ck804, jiffies is moving.
>
> The timer is wired different on nvidia than on 8111. They can
> go either through the 8259 or through the IOAPIC. There is still
> some code that falls back to the 8259 if IOAPIC doesn't work,
> which may make it appear working on Nvidia.
>
> As a warning I'm about to remove that code so don't rely on it.
>
> > If I don't change BSP apic id ( keep it to 0), It changes....
> >
> > I have no idea how the jiffies changes, there is another thread change
> it....?
>
> They change when interrupt 0 fires. So it's probably misrouted
> or similar.
>
>
> -Andi
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2005-10-28 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 19:49 Lu, Yinghai
2005-10-28 20:19 ` Yinghai Lu [this message]
2005-10-28 21:24 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-10-28 18:42 Yinghai Lu
2005-10-28 18:53 ` Andi Kleen
2006-01-06 2:04 ` yhlu
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=86802c440510281319y667427fj38ffd7a37b8cb77b@mail.gmail.com \
--to=yinghai.lu@amd.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxbios@openbios.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
all inboxes | Powered by JetHome®