From: ebiederm@xmission.com (Eric W. Biederman)
To: yhlu <yhlu.kernel@gmail.com>
Cc: Andi Kleen <ak@muc.de>,
ebiederm@xmission.com, Vivek Goyal <vgoyal@in.ibm.com>,
Fastboot mailing list <fastboot@lists.osdl.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Morton Andrew Morton <akpm@osdl.org>
Subject: Re: Inclusion of x86_64 memorize ioapic at bootup patch
Date: Sat, 07 Jan 2006 05:46:51 -0700 [thread overview]
Message-ID: <m1ek3k2ojo.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <86802c440601070143v44ee9f4dua2dcef2a536d4c73@mail.gmail.com> (yhlu.kernel@gmail.com's message of "Sat, 7 Jan 2006 01:43:22 -0800")
yhlu <yhlu.kernel@gmail.com> writes:
> andi,
>
> In LinuxBIOS, we don't set the MPS 0x467 and the AP still can be started by BSP.
>
> are these really needed for x86_64?
>
> Dprintk("Setting warm reset code and vector.\n");
>
> CMOS_WRITE(0xa, 0xf);
> local_flush_tlb();
> Dprintk("1.\n");
> *((volatile unsigned short *) phys_to_virt(0x469)) = start_rip >> 4;
> Dprintk("2.\n");
> *((volatile unsigned short *) phys_to_virt(0x467)) = start_rip & 0xf;
> Dprintk("3.\n");
>
> the STARTUP IPI should work well with MPS v1.4
There are very large x86 machines that a reset is sent to the remote
cpu and thus 0x40:0x67 and 0x40:0x67 becomes relevant.
YH you didn't do something foolish and put a linuxbios table below
0x500 did you?
Eric
next prev parent reply other threads:[~2006-01-07 12:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 1:32 Lu, Yinghai
2006-01-07 2:32 ` yhlu
2006-01-07 6:38 ` yhlu
2006-01-07 7:20 ` yhlu
2006-01-07 9:43 ` yhlu
2006-01-07 12:46 ` Eric W. Biederman [this message]
2006-01-07 19:36 ` yhlu
2006-01-07 19:44 ` Eric W. Biederman
2006-01-07 21:35 ` yhlu
-- strict thread matches above, loose matches on Subject: below --
2006-01-07 0:35 Lu, Yinghai
2006-01-07 1:14 ` Eric W. Biederman
2006-01-03 4:46 Vivek Goyal
2006-01-06 0:30 ` Yinghai Lu
2006-01-06 0:38 ` Andrew Morton
2006-01-06 4:50 ` Vivek Goyal
2006-01-06 8:02 ` Eric W. Biederman
2006-01-06 18:59 ` Andi Kleen
2006-01-06 8:24 ` Eric W. Biederman
2006-01-06 23:48 ` Andi Kleen
2006-01-07 0:00 ` Yinghai Lu
2006-01-07 0:29 ` Eric W. Biederman
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=m1ek3k2ojo.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.com \
--cc=yhlu.kernel@gmail.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
Powered by JetHome