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>,
	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 08:43:59 -0700	[thread overview]
Message-ID: <20070910154358.GA24627@askeshav-devel.jf.intel.com> (raw)
In-Reply-To: <20070909111619.GF31099@rhun.haifa.ibm.com>

On Sun, Sep 09, 2007 at 02:16:19PM +0300, Muli Ben-Yehuda wrote:
> On Sat, Sep 08, 2007 at 01:05:24PM -0700, Keshavamurthy, Anil S wrote:
> 
> > Subject: [RFC][Intel-IOMMU] Fix for IOMMU early crash
> 
> This patch feels like a huge hack. See below.
You seem to be jumping to conclusion without going
in detail. The pci_dev struct contains pointer to sysdata,
which in turn points to the copy of its parent's bus sysdata.
So technically speaking we can eliminate sysdata pointer from
pci_dev struct which is what one portion of this patch does.

> 
> > 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.
> 
> Hmpf, why is this needed? with the pci_sysdata work that recently went
> into mainline we have a void *iommu member in pci_sysdata which should
> be all that's needed. Please elaborate if it's not enough for your
> needs.
I looked at your patch and it was not suitable because I need to store
iommu private pointer in pci_dev and not in the pci_bus. So I have added
a new member sys_data in the pci_dev struct. I can change the name from 
sys_dev to iomu_priv to clear the confusion. Do let me know.


-Anil






> 
> Thanks,
> Muli

  reply	other threads:[~2007-09-09 15:31 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 [this message]
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
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=20070910154358.GA24627@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 \
    /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