mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>,
	Paul Mackerras <paulus@samba.org>,
	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: Tue, 11 Sep 2007 13:43:59 -0700	[thread overview]
Message-ID: <20070911204359.GA29380@askeshav-devel.jf.intel.com> (raw)
In-Reply-To: <20070910202543.GS4374@rhun.haifa.ibm.com>

On Mon, Sep 10, 2007 at 11:25:43PM +0300, Muli Ben-Yehuda wrote:
> On Tue, Sep 11, 2007 at 10:42:31AM -0700, Keshavamurthy, Anil S wrote:
> 
> > Yes, I agree that pci_dev->sysdata can;t be removed. Even we (IOMMU)
> > were dependent on this field but somehow this field is being
> > overwritten to point to pci_bus's->sysdata and hence IOMMU was
> > failing. Earlier it was overwritten to NULL and hence we were not
> > failing but now it is overwritten to non-NULL and hence we fail.
> 
> Do you know which commit caused that change?
> 
> > My therory is that we don;t need to copy pci_bus's->sysdata to 
> > pci_dev's->sysdata. Below patch solves my problem.
> > Any objection to below patch?
> 
> I will give it a spin to verify it works for me, but in general I am
> wary of making such changes unless we can verify (read: audit) that
> they have no adverse side effects *on all architectures*.
Thanks Muli for your help here. I tested on x86_64 and saw no
issues. Looking at the code, pci_dev's->sysdata becomes useless 
if the intent here is to keep a copy of it's bus's->sysdata as
the same can be obtained from pci_dev->bus->sysdata.

Thanks,
Anil

  reply	other threads:[~2007-09-10 20:32 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
2007-09-11 17:42   ` Keshavamurthy, Anil S
2007-09-10 20:25     ` Muli Ben-Yehuda
2007-09-11 20:43       ` Keshavamurthy, Anil S [this message]
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=20070911204359.GA29380@askeshav-devel.jf.intel.com \
    --to=anil.s.keshavamurthy@intel.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muli@il.ibm.com \
    --cc=paulus@samba.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

Powered by JetHome