From: William Lee Irwin III <wli@holomorphy.com>
To: Matthew Dobson <colpatch@us.ibm.com>,
linux-kernel@vger.kernel.org, Martin.Bligh@us.ibm.com,
hohnbaum@us.ibm.com
Subject: Re: [0/4] NUMA-Q: remove PCI bus number mangling
Date: Tue, 12 Nov 2002 13:48:04 -0800 [thread overview]
Message-ID: <20021112214804.GX23425@holomorphy.com> (raw)
In-Reply-To: <20021112213504.GV23425@holomorphy.com>
On Tue, Nov 12, 2002 at 01:35:04PM -0800, William Lee Irwin III wrote:
> I'll remove the bus number mangling from it so it uses ->sysdata
> instead, make it an additional stage of the patch series and convert
> arch/i386/pci/numa.c to use it instead.
> Bus number mangling has been vetoed numerous times; the agreed-upon
> method of dealing with this is stuffing arch-private information in
> ->sysdata and dispatching on that within PCI config access routines.
[7/4] NUMA-Q: introduce __pcibus_to_node()
This introduces a generic __pcibus_to_node() method in asm/topology.h
and provides a NUMA-Q -specific implementation.
asm-generic/topology.h | 3 +++
asm-i386/topology.h | 4 ++++
2 files changed, 7 insertions(+)
diff -urpN pci-2.5.47-6/include/asm-generic/topology.h pci-2.5.47-7/include/asm-generic/topology.h
--- pci-2.5.47-6/include/asm-generic/topology.h 2002-11-10 19:28:04.000000000 -0800
+++ pci-2.5.47-7/include/asm-generic/topology.h 2002-11-12 13:03:40.000000000 -0800
@@ -47,5 +47,8 @@
#ifndef __node_to_memblk
#define __node_to_memblk(node) (0)
#endif
+#ifndef __pcibus_to_node
+#define __pcibus_to_node(bus) (0)
+#endif
#endif /* _ASM_GENERIC_TOPOLOGY_H */
diff -urpN pci-2.5.47-6/include/asm-i386/topology.h pci-2.5.47-7/include/asm-i386/topology.h
--- pci-2.5.47-6/include/asm-i386/topology.h 2002-11-10 19:28:05.000000000 -0800
+++ pci-2.5.47-7/include/asm-i386/topology.h 2002-11-12 13:04:43.000000000 -0800
@@ -83,6 +83,10 @@ static inline unsigned long __node_to_cp
/* Returns the number of the first MemBlk on Node 'node' */
#define __node_to_memblk(node) (node)
+/* Returns the number of the node containing PCI bus 'bus' */
+#define __pcibus_to_node(bus) ((int)((bus)->sysdata))
+
+
#else /* !CONFIG_X86_NUMAQ */
/*
* Other i386 platforms should define their own version of the
next prev parent reply other threads:[~2002-11-12 21:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 12:37 [0/4] NUMA-Q: remove PCI bus number mangling William Lee Irwin III
2002-11-12 20:52 ` William Lee Irwin III
2002-11-12 20:55 ` William Lee Irwin III
2002-11-12 21:29 ` Matthew Dobson
2002-11-12 21:35 ` William Lee Irwin III
2002-11-12 21:39 ` William Lee Irwin III
2002-11-12 22:46 ` Martin J. Bligh
2002-11-12 21:53 ` William Lee Irwin III
2002-11-12 23:53 ` Martin J. Bligh
2002-11-12 22:59 ` William Lee Irwin III
2002-11-12 23:19 ` William Lee Irwin III
2002-11-12 23:58 ` William Lee Irwin III
2002-11-13 0:04 ` Greg KH
2002-11-13 0:12 ` William Lee Irwin III
2002-11-13 0:20 ` Greg KH
2002-11-13 0:28 ` William Lee Irwin III
2002-11-13 1:01 ` William Lee Irwin III
2002-11-13 12:07 ` Ivan Kokshaysky
2002-11-13 20:59 ` William Lee Irwin III
2002-11-13 10:10 ` William Lee Irwin III
2002-11-13 11:20 ` William Lee Irwin III
2003-01-01 9:28 ` William Lee Irwin III
2002-11-12 21:48 ` William Lee Irwin III [this message]
2002-11-12 21:48 ` William Lee Irwin III
2002-11-12 20:53 ` William Lee Irwin III
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=20021112214804.GX23425@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=colpatch@us.ibm.com \
--cc=hohnbaum@us.ibm.com \
--cc=linux-kernel@vger.kernel.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