From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: linux-kernel@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Olaf Kirch <okir@suse.de>, Greg KH <gregkh@suse.de>,
Tony Luck <tony.luck@intel.com>,
Becky Bruce <beckyb@kernel.crashing.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Kumar Gala <galak@kernel.crashing.org>,
x86@kernel.org, linux-ia64@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 6/9] swiotlb: use dma_to_phys and phys_to_dma
Date: Fri, 29 May 2009 21:09:16 +0000 [thread overview]
Message-ID: <4A204EFC.501@goop.org> (raw)
In-Reply-To: <1243586643-5554-7-git-send-email-ian.campbell@citrix.com>
Ian Campbell wrote:
> static dma_addr_t swiotlb_virt_to_bus(struct device *hwdev,
> volatile void *address)
> {
> - return swiotlb_phys_to_bus(hwdev, virt_to_phys(address));
> + return phys_to_dma(hwdev, virt_to_phys(address));
> }
>
> void * __weak swiotlb_bus_to_virt(struct device *hwdev, dma_addr_t address)
>
Does this need to be weak too?
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: x86@kernel.org, Tony Luck <tony.luck@intel.com>,
linux-ia64@vger.kernel.org, Olaf Kirch <okir@suse.de>,
Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 6/9] swiotlb: use dma_to_phys and phys_to_dma
Date: Fri, 29 May 2009 14:09:16 -0700 [thread overview]
Message-ID: <4A204EFC.501@goop.org> (raw)
In-Reply-To: <1243586643-5554-7-git-send-email-ian.campbell@citrix.com>
Ian Campbell wrote:
> static dma_addr_t swiotlb_virt_to_bus(struct device *hwdev,
> volatile void *address)
> {
> - return swiotlb_phys_to_bus(hwdev, virt_to_phys(address));
> + return phys_to_dma(hwdev, virt_to_phys(address));
> }
>
> void * __weak swiotlb_bus_to_virt(struct device *hwdev, dma_addr_t address)
>
Does this need to be weak too?
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: linux-kernel@vger.kernel.org,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Olaf Kirch <okir@suse.de>, Greg KH <gregkh@suse.de>,
Tony Luck <tony.luck@intel.com>,
Becky Bruce <beckyb@kernel.crashing.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Kumar Gala <galak@kernel.crashing.org>,
x86@kernel.org, linux-ia64@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 6/9] swiotlb: use dma_to_phys and phys_to_dma
Date: Fri, 29 May 2009 14:09:16 -0700 [thread overview]
Message-ID: <4A204EFC.501@goop.org> (raw)
In-Reply-To: <1243586643-5554-7-git-send-email-ian.campbell@citrix.com>
Ian Campbell wrote:
> static dma_addr_t swiotlb_virt_to_bus(struct device *hwdev,
> volatile void *address)
> {
> - return swiotlb_phys_to_bus(hwdev, virt_to_phys(address));
> + return phys_to_dma(hwdev, virt_to_phys(address));
> }
>
> void * __weak swiotlb_bus_to_virt(struct device *hwdev, dma_addr_t address)
>
Does this need to be weak too?
J
next prev parent reply other threads:[~2009-05-29 21:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 8:43 Ian Campbell
2009-05-29 8:43 ` Ian Campbell
2009-05-29 8:43 ` Ian Campbell
2009-05-29 8:43 ` [PATCH 1/9] ia64: introduce arch-specific dma-mapping interfaces Ian Campbell
2009-05-29 8:43 ` Ian Campbell
2009-05-29 8:43 ` [PATCH 2/9] x86: introduce arch-specific dma-mapping interface Ian Campbell
2009-05-29 8:43 ` [PATCH 3/9] x86: use dma_map_range when allocating PCI DMA memory Ian Campbell
2009-05-29 8:43 ` [PATCH 4/9] x86: use dma_map_range when allocating PCI DMA memory with no IOMMU Ian Campbell
2009-05-29 8:43 ` [PATCH 5/9] x86: use dma_map_range when allocating PCI GART memory Ian Campbell
2009-05-29 8:44 ` [PATCH 6/9] swiotlb: use dma_to_phys and phys_to_dma Ian Campbell
2009-05-29 8:44 ` Ian Campbell
2009-05-29 8:44 ` Ian Campbell
2009-05-29 21:09 ` Jeremy Fitzhardinge [this message]
2009-05-29 21:09 ` Jeremy Fitzhardinge
2009-05-29 21:09 ` Jeremy Fitzhardinge
2009-05-30 13:02 ` Ian Campbell
2009-05-30 13:02 ` Ian Campbell
2009-05-30 13:02 ` Ian Campbell
2009-05-29 8:44 ` [PATCH 7/9] swiotlb: use dma_map_range Ian Campbell
2009-05-29 8:44 ` Ian Campbell
2009-05-29 8:44 ` Ian Campbell
2009-05-29 8:44 ` [PATCH 8/9] swiotlb: support HIGHMEM in swiotlb_bus_to_virt Ian Campbell
2009-05-29 8:44 ` Ian Campbell
2009-05-29 15:58 ` Jeremy Fitzhardinge
2009-05-29 15:58 ` Jeremy Fitzhardinge
2009-05-30 13:02 ` Ian Campbell
2009-05-30 13:02 ` Ian Campbell
2009-05-29 8:44 ` [PATCH 9/9] swiotlb: rename swiotlb_virt_to_bus as virt_to_dma Ian Campbell
2009-05-29 9:06 ` swiotlb: Introduce architecture-specific APIs to replace Ian Campbell
2009-05-29 9:06 ` swiotlb: Introduce architecture-specific APIs to replace __weak functions Ian Campbell
2009-05-29 9:06 ` Ian Campbell
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=4A204EFC.501@goop.org \
--to=jeremy@goop.org \
--cc=beckyb@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=galak@kernel.crashing.org \
--cc=gregkh@suse.de \
--cc=ian.campbell@citrix.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=okir@suse.de \
--cc=tony.luck@intel.com \
--cc=x86@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.