From: Arjan van de Ven <arjan@infradead.org>
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: Andi Kleen <ak@suse.de>, Jeff Garzik <jeff@garzik.org>,
Yinghai Lu <Yinghai.Lu@Sun.COM>, Andrew Morton <akpm@osdl.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Jon Mason <jdmason@gmail.com>
Subject: Re: [PATCH 1/1] x86-64: introduce struct pci_sysdata to facilitate sharing of ->sysdata
Date: Thu, 12 Jul 2007 09:17:31 +0800 [thread overview]
Message-ID: <1184203051.2693.3.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20070711134514.GA4789@rhun.haifa.ibm.com>
On Wed, 2007-07-11 at 16:45 +0300, Muli Ben-Yehuda wrote:
> Andi, please consider applying for 2.6.23. Applies on top of the
> Calgary update I just sent out ("Calgary: more updates for 2.6.23").
>
> This patch introduces struct pci_sysdata to x86 and x86-64, and
> converts the existing two users (NUMA, Calgary) to use it.
>
> This lays the groundwork for having other users of sysdata, such as
> the PCI domains work.
>
> The Calgary bits are tested, the NUMA bits just look ok.
I very much start to dislike the untyped "sysdata"... I much rather have
separate fields for the different uses (like a IOMMU field) that aren't
going to share ever. Possibly even typed, but for IOMMU that may be
tricky....
next prev parent reply other threads:[~2007-07-12 1:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 13:45 [PATCH 1/1] x86-64: introduce struct pci_sysdata to facilitate sharing of ->sysdata Muli Ben-Yehuda
2007-07-11 16:41 ` Yinghai Lu
2007-07-11 17:50 ` Muli Ben-Yehuda
2007-07-12 1:17 ` Arjan van de Ven [this message]
2007-07-12 9:10 ` Muli Ben-Yehuda
2007-07-12 9:13 ` Arjan van de Ven
2007-07-12 9:17 ` Muli Ben-Yehuda
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=1184203051.2693.3.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=Yinghai.Lu@Sun.COM \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jdmason@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.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