From: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Muli Ben-Yehuda <muli@il.ibm.com>,
Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] stop x86 ->sysdata abuse; introduce pci_sysdata
Date: Mon, 4 Jun 2007 16:27:36 -0700 [thread overview]
Message-ID: <20070604232736.GA11981@linux-os.sc.intel.com> (raw)
In-Reply-To: <20070604210551.GH20299@havoc.gtf.org>
On Mon, Jun 04, 2007 at 05:05:51PM -0400, Jeff Garzik wrote:
>
> This patch introduces struct pci_sysdata to x86 and x86-64, and
> converts the existing two users (NUMA, Calgary) to use it.
>
> This eliminates the conflict between NUMA and Calgary using the same
> pointer for different uses, and lays the groundwork for adding x86
> PCI domain support.
>
> Signed-off-by: Jeff Garzik <jeff@garzik.org>
>
> ---
>
> NOTE: This patch is untested, extract from the larger changes found in
> jgarzik/misc-2.6.git#pciseg. Hopefully NUMA and/or Calgary users will
> test and ack this, then build patches on top of it.
Looks like the recently announced Intel-IOMMU too (just like Calgary)
depends on sysdata. I will modify my Intel-IOMMU accordingly and
will let you know how it goes with your patch.
thanks,
Anil
next prev parent reply other threads:[~2007-06-04 23:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 8:05 Calgary updates for 2.6.23 muli
2007-05-22 8:05 ` [PATCH 1/15] x86-64: Calgary - generalize calgary_increase_split_completion_timeout muli
2007-05-22 8:05 ` [PATCH 2/15] x86-64: Calgary - update copyright notice muli
2007-05-22 8:05 ` [PATCH 3/15] x86-64: Calgary - introduce handle_quirks() for various chipset quirks muli
2007-05-22 8:05 ` [PATCH 4/15] x86-64: Calgary - introduce chipset specific ops muli
2007-05-22 8:05 ` [PATCH 5/15] x86-64: Calgary - abstract how we find the iommu_table for a device muli
2007-05-22 8:05 ` [PATCH 6/15] x86-64: Calgary - introduce CalIOC2 support muli
2007-05-22 8:05 ` [PATCH 7/15] x86-64: Calgary - add chip_ops and a quirk function for CalIOC2 muli
2007-05-22 8:05 ` [PATCH 8/15] x86-64: Calgary - implement CalIOC2 TCE cache flush sequence muli
2007-05-22 8:05 ` [PATCH 9/15] x86-64: Calgary - make dump_error_regs a chip op muli
2007-05-22 8:05 ` [PATCH 10/15] x86-64: Calgary - grab PLSSR too when a DMA error occurs muli
2007-05-22 8:06 ` [PATCH 11/15] x86-64: Calgary - reserve TCEs with the same address as MEM regions muli
2007-05-22 8:06 ` [PATCH 12/15] x86-64: Calgary - cleanup of unneeded macros muli
2007-05-22 8:06 ` [PATCH 13/15] x86-64: Calgary - tabify and trim trailing whitespace muli
2007-05-22 8:06 ` [PATCH 14/15] x86-64: Calgary - only reserve the first 1MB of IO space for CalIOC2 muli
2007-05-22 8:06 ` [PATCH 15/15] x86-64: Calgary - tidy up debug printks muli
[not found] ` <20070604113344.0e71ca8c.akpm@linux-foundation.org>
2007-06-04 19:06 ` [PATCH 5/15] x86-64: Calgary - abstract how we find the iommu_table for a device Jeff Garzik
2007-06-04 19:13 ` Muli Ben-Yehuda
2007-06-04 19:31 ` Jeff Garzik
2007-06-04 21:05 ` [PATCH] stop x86 ->sysdata abuse; introduce pci_sysdata Jeff Garzik
2007-06-04 23:27 ` Keshavamurthy, Anil S [this message]
2007-06-05 10:29 ` Muli Ben-Yehuda
2007-06-06 21:03 ` Muli Ben-Yehuda
2007-06-06 21:21 ` Jeff Garzik
2007-06-06 21:26 ` 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=20070604232736.GA11981@linux-os.sc.intel.com \
--to=anil.s.keshavamurthy@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--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 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.