mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>
Cc: akpm@osdl.org, Greg KH <greg@kroah.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	kristen.c.accardi@intel.com
Subject: Re: [RFC][Intel-IOMMU] Fix for IOMMU early crash
Date: Mon, 10 Sep 2007 03:37:48 +1000	[thread overview]
Message-ID: <18148.12140.21118.252581@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20070908200523.GA16204@askeshav-devel.jf.intel.com>

Keshavamurthy, Anil S writes:

> Subject: [RFC][Intel-IOMMU] Fix for IOMMU early crash
> 
> Populating pci_bus->sysdata way early in the pci discovery phase
> sets NON-NULL value to pci_dev->sysdata which breaks the assumption
> in the Intel IOMMU driver and crashes the system.
> 
> 
> In the drivers/pci/probe.c, pci_dev->sysdata gets a copy of
> its pci_bus->sysdata which is not required as
> the same can be obtained from pci_dev->bus->sysdata. More over 
> the left hand assignment of pci_dev->sysdata is never being used,

Wrong.  You needed to grep a bit more widely...

> so their is no point is setting 
> pci_dev->sysdata = pci_bus->sysdata;
> 
> This patch removes sysdata from pci_dev struct and creates a new
> field called sys_data which is exclusively used 
> by IOMMU driver to keep its per device context pointer.

This will break powerpc, because we use the pci_dev->sysdata field to
point to a firmware device tree node.  Please figure out another way
to solve your problem.

Paul.

  parent reply	other threads:[~2007-09-09 20:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-08 20:05 Keshavamurthy, Anil S
2007-09-09 11:16 ` Muli Ben-Yehuda
2007-09-10 15:43   ` Keshavamurthy, Anil S
2007-09-09 17:51     ` Muli Ben-Yehuda
2007-09-11 17:22       ` Keshavamurthy, Anil S
2007-09-09 17:37 ` Paul Mackerras [this message]
2007-09-11 17:42   ` Keshavamurthy, Anil S
2007-09-10 20:25     ` Muli Ben-Yehuda
2007-09-11 20:43       ` Keshavamurthy, Anil S
2007-09-12 19:28     ` [patch][Intel-IOMMU] " Keshavamurthy, Anil S
2007-09-11 19:48       ` Paul Mackerras
2007-09-12 21:55         ` Keshavamurthy, Anil S
2007-09-11 22:05           ` [BUG:] forcedeth: MCP55 not allowing DHCP Casey Dahlin
2007-09-18  1:59             ` Casey Dahlin
2007-09-13  1:29         ` [patch][Intel-IOMMU] Fix for IOMMU early crash Keshavamurthy, Anil S
2007-09-14 16:30           ` Paul Mackerras
2007-09-25 17:07             ` Keshavamurthy, Anil S
2007-10-03 21:13         ` [patch take 2][Intel-IOMMU] " Keshavamurthy, Anil S
2007-10-04  1:19           ` Benjamin Herrenschmidt
2007-10-04  1:36             ` Keshavamurthy, Anil S
2007-10-04  3:39               ` Benjamin Herrenschmidt
2007-10-04 19:20                 ` Keshavamurthy, Anil S
2007-10-05  3:08                   ` Benjamin Herrenschmidt

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=18148.12140.21118.252581@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=akpm@osdl.org \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=greg@kroah.com \
    --cc=kristen.c.accardi@intel.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

all inboxes | Powered by JetHome®