linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: yhlu <yhlu.kernel@gmail.com>
To: ebiederm@xmission.com
Cc: Andi Kleen <ak@muc.de>, 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: Fri, 6 Jan 2006 18:32:09 -0800	[thread overview]
Message-ID: <86802c440601061832m4898e20fw4c9a8360e85cfa17@mail.gmail.com> (raw)
In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A42030949CB@ssvlexmb2.amd.com>

some code clear 3 byte in mptable from 0x468

00000460: 41 01 09 12 03 00 0f 00 41 02 09 13 03 00 0f 00
00000470: 41 03 09 10 03 03 05 00 43 00 ff 00 03 01 05 00
00000480: 43 00 ff 01

00000460: 41 01 09 12 03 00 0f 00 00 00 00 13 03 00 0f 00
00000470: 41 03 09 10 03 03 05 00 43 00 ff 00 03 01 05 00
00000480: 43 00 ff 01

it is third irq entry for pcie slot....

//Slot  PCIE x4
        for(i=0;i<4;i++) {
                smp_write_intsrc(mc, mp_INT,
MP_IRQ_TRIGGER_LEVEL|MP_IRQ_POLARITY_LOW, bus_ck804b_4, (0x00<<2)|i,
apicid_ck804b, 0x10 + (1+i+4-sbdnb%4)%4);
        }


/*Local Ints:   Type    Polarity    Trigger     Bus ID   IRQ    APIC ID PIN#*/
        smp_write_intsrc(mc, mp_ExtINT,
MP_IRQ_TRIGGER_EDGE|MP_IRQ_POLARITY_HIGH, bus_isa, 0x0, MP_APIC_ALL,
0x0);
        smp_write_intsrc(mc, mp_NMI,
MP_IRQ_TRIGGER_EDGE|MP_IRQ_POLARITY_HIGH, bus_isa, 0x0, MP_APIC_ALL,
0x1);

the range already in e820 reserved area...

Bootdata ok (command line is apic=debug pci=routeirq
ramdisk_size=65536 root=/dev/ram0 rw console=tty0
console=ttyS0,115200n8 )
Linux version 2.6.15-gdb9edfd7 (root@yhlunb) (gcc version 4.0.2
20050901 (prerelease) (SUSE Linux)) #13 SMP Fri Jan 6 17:58:25 PST
2006
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 0000000000000e7c (reserved)
 BIOS-e820: 0000000000000e7c - 00000000000a0000 (usable)
 BIOS-e820: 00000000000f0000 - 00000000000f0400 (reserved)
 BIOS-e820: 0000000000100000 - 00000000c0000000 (usable)
 BIOS-e820: 0000000100000000 - 0000000240000000 (usable)

YH

  reply	other threads:[~2006-01-07  2:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-07  1:32 Inclusion of x86_64 memorize ioapic at bootup patch Lu, Yinghai
2006-01-07  2:32 ` yhlu [this message]
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
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=86802c440601061832m4898e20fw4c9a8360e85cfa17@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@in.ibm.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;
as well as URLs for NNTP newsgroup(s).