From: Matthew Wilcox <matthew@wil.cx>
To: Jeremy Higdon <jeremy@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
jesse.barnes@intel.com, habeck@sgi.com,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH 1/1] Fix PCI DMA flag propagation on SN (Altix) with PICs
Date: Fri, 27 Feb 2009 19:21:17 +0000 [thread overview]
Message-ID: <20090227192116.GO16891@parisc-linux.org> (raw)
In-Reply-To: <20090227093835.GA306198@sgi.com>
On Fri, Feb 27, 2009 at 01:38:35AM -0800, Jeremy Higdon wrote:
> We recently discovered a problem with passing of DMA attributes on
> SN systems with the older PIC chips.
I think this should go in through the ia64 tree, not the PCI tree ...
> Signed-off-by: Jeremy Higdon <jeremy@sgi.com>
>
> --- a/arch/ia64/sn/pci/pcibr/pcibr_dma.c 2009-02-25 23:29:21.000000000 -0800
> +++ b/arch/ia64/sn/pci/pcibr/pcibr_dma.c 2009-02-25 23:29:09.318611870 -0800
> @@ -135,11 +135,10 @@ pcibr_dmatrans_direct64(struct pcidev_in
> if (SN_DMA_ADDRTYPE(dma_flags) = SN_DMA_ADDR_PHYS)
> pci_addr = IS_PIC_SOFT(pcibus_info) ?
> PHYS_TO_DMA(paddr) :
> - PHYS_TO_TIODMA(paddr) | dma_attributes;
> + PHYS_TO_TIODMA(paddr);
> else
> - pci_addr = IS_PIC_SOFT(pcibus_info) ?
> - paddr :
> - paddr | dma_attributes;
> + pci_addr = paddr;
> + pci_addr |= dma_attributes;
>
> /* Handle Bus mode */
> if (IS_PCIX(pcibus_info))
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <matthew@wil.cx>
To: Jeremy Higdon <jeremy@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
jesse.barnes@intel.com, habeck@sgi.com,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH 1/1] Fix PCI DMA flag propagation on SN (Altix) with PICs
Date: Fri, 27 Feb 2009 12:21:17 -0700 [thread overview]
Message-ID: <20090227192116.GO16891@parisc-linux.org> (raw)
In-Reply-To: <20090227093835.GA306198@sgi.com>
On Fri, Feb 27, 2009 at 01:38:35AM -0800, Jeremy Higdon wrote:
> We recently discovered a problem with passing of DMA attributes on
> SN systems with the older PIC chips.
I think this should go in through the ia64 tree, not the PCI tree ...
> Signed-off-by: Jeremy Higdon <jeremy@sgi.com>
>
> --- a/arch/ia64/sn/pci/pcibr/pcibr_dma.c 2009-02-25 23:29:21.000000000 -0800
> +++ b/arch/ia64/sn/pci/pcibr/pcibr_dma.c 2009-02-25 23:29:09.318611870 -0800
> @@ -135,11 +135,10 @@ pcibr_dmatrans_direct64(struct pcidev_in
> if (SN_DMA_ADDRTYPE(dma_flags) == SN_DMA_ADDR_PHYS)
> pci_addr = IS_PIC_SOFT(pcibus_info) ?
> PHYS_TO_DMA(paddr) :
> - PHYS_TO_TIODMA(paddr) | dma_attributes;
> + PHYS_TO_TIODMA(paddr);
> else
> - pci_addr = IS_PIC_SOFT(pcibus_info) ?
> - paddr :
> - paddr | dma_attributes;
> + pci_addr = paddr;
> + pci_addr |= dma_attributes;
>
> /* Handle Bus mode */
> if (IS_PCIX(pcibus_info))
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-02-27 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 9:38 [PATCH 1/1] Fix PCI DMA flag propagation on SN (Altix) with PICs Jeremy Higdon
2009-02-27 19:08 ` Jesse Barnes
2009-02-27 19:21 ` Matthew Wilcox [this message]
2009-02-27 19:21 ` Matthew Wilcox
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=20090227192116.GO16891@parisc-linux.org \
--to=matthew@wil.cx \
--cc=habeck@sgi.com \
--cc=jeremy@sgi.com \
--cc=jesse.barnes@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 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.