From: Roland Dreier <rdreier@cisco.com>
To: Grant Grundler <iod00d@hp.com>
Cc: "Luck, Tony" <tony.luck@intel.com>, Chris Wedgwood <cw@f00f.org>,
Grant Grundler <grundler@parisc-linux.org>,
Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-ia64@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
"Miller, Mike (OS Dev)" <Mike.Miller@hp.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Problems with MSI-X on ia64
Date: Fri, 17 Feb 2006 20:21:37 +0000 [thread overview]
Message-ID: <aday809d9da.fsf@cisco.com> (raw)
In-Reply-To: <20060217200454.GA24942@esmail.cup.hp.com> (Grant Grundler's message of "Fri, 17 Feb 2006 12:04:54 -0800")
BARs above 4G on i386 raise all sorts of issues. I think Grant's
original patch (which changes phys_addr in drivers/pci/msi.c to
unsigned long) is correct as it stands, because the MSI code is going
to use that address to ioremap() the MSI-X table. And the address
passed to ioremap is unsigned long anyway.
Some extension like ioremap_pfn() or something like that is going to
needed to handling giving the kernel access to BARs above 4G on 32-bit
archs.
- R.
WARNING: multiple messages have this Message-ID (diff)
From: Roland Dreier <rdreier@cisco.com>
To: Grant Grundler <iod00d@hp.com>
Cc: "Luck, Tony" <tony.luck@intel.com>, Chris Wedgwood <cw@f00f.org>,
Grant Grundler <grundler@parisc-linux.org>,
Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-ia64@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
"Miller, Mike (OS Dev)" <Mike.Miller@hp.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Problems with MSI-X on ia64
Date: Fri, 17 Feb 2006 12:21:37 -0800 [thread overview]
Message-ID: <aday809d9da.fsf@cisco.com> (raw)
In-Reply-To: <20060217200454.GA24942@esmail.cup.hp.com> (Grant Grundler's message of "Fri, 17 Feb 2006 12:04:54 -0800")
BARs above 4G on i386 raise all sorts of issues. I think Grant's
original patch (which changes phys_addr in drivers/pci/msi.c to
unsigned long) is correct as it stands, because the MSI code is going
to use that address to ioremap() the MSI-X table. And the address
passed to ioremap is unsigned long anyway.
Some extension like ioremap_pfn() or something like that is going to
needed to handling giving the kernel access to BARs above 4G on 32-bit
archs.
- R.
next prev parent reply other threads:[~2006-02-17 20:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 17:14 Problems with MSI-X on ia64 Miller, Mike (OS Dev)
2006-01-26 17:14 ` Miller, Mike (OS Dev)
2006-01-26 17:14 ` Miller, Mike (OS Dev)
2006-01-26 17:24 ` Mark Maule
2006-01-26 17:24 ` Mark Maule
2006-01-26 20:24 ` Grant Grundler
2006-01-26 20:24 ` Grant Grundler
2006-01-26 20:37 ` Miller, Mike (OS Dev)
2006-01-26 20:37 ` Miller, Mike (OS Dev)
2006-01-26 20:37 ` Miller, Mike (OS Dev)
2006-01-27 4:37 ` Greg KH
2006-01-27 4:37 ` Greg KH
2006-01-27 15:34 ` Miller, Mike (OS Dev)
2006-01-27 15:34 ` Miller, Mike (OS Dev)
2006-01-27 15:34 ` Miller, Mike (OS Dev)
2006-02-17 7:58 ` Grant Grundler
2006-02-17 7:58 ` Grant Grundler
2006-02-17 8:46 ` Chris Wedgwood
2006-02-17 8:46 ` Chris Wedgwood
2006-02-17 14:11 ` Matthew Wilcox
2006-02-17 14:11 ` Matthew Wilcox
2006-02-17 16:36 ` Grant Grundler
2006-02-17 16:36 ` Grant Grundler
2006-02-17 19:10 ` Chris Wedgwood
2006-02-17 19:10 ` Chris Wedgwood
2006-06-01 6:35 ` Grant Grundler
2006-06-01 6:35 ` Grant Grundler
2006-02-17 19:52 ` Luck, Tony
2006-02-17 19:52 ` Luck, Tony
2006-02-17 19:52 ` Luck, Tony
2006-02-17 20:04 ` Grant Grundler
2006-02-17 20:04 ` Grant Grundler
2006-02-17 20:21 ` Roland Dreier [this message]
2006-02-17 20:21 ` Roland Dreier
2006-02-21 20:21 ` Miller, Mike (OS Dev)
2006-02-21 20:21 ` Miller, Mike (OS Dev)
2006-02-21 20:21 ` Miller, Mike (OS Dev)
2006-02-25 16:23 ` Grant Grundler
2006-02-25 16:23 ` Grant Grundler
2006-02-27 18:36 ` Miller, Mike (OS Dev)
2006-02-27 18:36 ` Miller, Mike (OS Dev)
2006-02-27 18:36 ` Miller, Mike (OS Dev)
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=aday809d9da.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=Mike.Miller@hp.com \
--cc=cw@f00f.org \
--cc=gregkh@suse.de \
--cc=grundler@parisc-linux.org \
--cc=iod00d@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linux-scsi@vger.kernel.org \
--cc=tony.luck@intel.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.