From: Brian Gerst <bgerst@didntduck.org>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] i386: Per node IDT
Date: Mon, 11 Jul 2005 11:03:03 -0400 [thread overview]
Message-ID: <42D28A27.9000507@didntduck.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0507110718500.16055@montezuma.fsmlabs.com>
Zwane Mwaikambo wrote:
> On Sun, 11 Jul 2005, Andi Kleen wrote:
>
>
>>Why per node? Why not go the whole way and make it per CPU?
>>
>>I would also not define it statically, but allocate it at boot time
>>in node local memory.
>
>
> I went per node so that it would be minimal/zero impact for the no-node
> case, it would also simplify hotplug cpu since once a cpu in a node goes
> down, we still have other participating processors capable of handling
> its devices without having to do too much migration work. I'll definitely
> incorporate the node local allocations however, for some i386 systems we
> might be forced to stick some additional IDTs on node 0 since the IDTR
> will only take 32bit addresses and we could end up with only highmem on
> some nodes.
Doesn't the IDTR take a virtual address? It has to or else the f00f bug
fix wouldn't work.
--
Brian Gerst
next prev parent reply other threads:[~2005-07-11 15:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.0507101617240.16055@montezuma.fsmlabs.com.suse.lists.linux.kernel>
2005-07-11 1:59 ` [RFC][PATCH] i386: Per node IDT Andi Kleen
2005-07-11 4:02 ` Arjan van de Ven
2005-07-11 4:08 ` Andi Kleen
2005-07-11 14:09 ` Zwane Mwaikambo
2005-07-11 14:05 ` Arjan van de Ven
2005-07-11 15:17 ` Kenji Kaneshige
2005-07-11 13:34 ` Zwane Mwaikambo
2005-07-11 15:03 ` Brian Gerst [this message]
2005-07-11 15:21 ` Zwane Mwaikambo
2005-07-11 16:39 ` Andi Kleen
2005-07-11 12:28 Oleg Nesterov
2005-07-11 14:03 ` Zwane Mwaikambo
2005-07-11 14:44 ` Oleg Nesterov
2005-07-11 15:05 ` Zwane Mwaikambo
2005-07-11 15:19 ` Oleg Nesterov
2005-08-07 1:13 ` Zwane Mwaikambo
2005-08-07 10:47 ` Oleg Nesterov
-- strict thread matches above, loose matches on Subject: below --
2005-07-10 22:41 Zwane Mwaikambo
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=42D28A27.9000507@didntduck.org \
--to=bgerst@didntduck.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.