From: Joerg Roedel <joerg.roedel@amd.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
davej@redhat.com, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [Bug 487894] New: sky2 0000:06:00.0: DMA-API: device driver frees DMA memory with different size
Date: Thu, 2 Apr 2009 17:29:17 +0200 [thread overview]
Message-ID: <20090402152917.GC4776@amd.com> (raw)
In-Reply-To: <20090402080806.047e2716@nehalam>
On Thu, Apr 02, 2009 at 08:08:06AM -0700, Stephen Hemminger wrote:
> On Thu, 2 Apr 2009 16:31:42 +0200
> Joerg Roedel <joerg.roedel@amd.com> wrote:
> > Author: Joerg Roedel <joerg.roedel@amd.com>
> > Date: Thu Apr 2 15:55:55 2009 +0200
> >
> > x86/dma: unify definition of pci_unmap_addr* and pci_unmap_len macros
> >
> > Impact: unification of pci-dma macros and pci_32h removal
> >
> > This patch unifies the definition of the pci_unmap_addr*, pci_unmap_len*
> > and DECLARE_PCI_UNMAP* macros. This makes sense because the pci_unmap
> > functions are no longer no-ops anymore when the kernel runs with
> > CONFIG_DMA_API_DEBUG. This also simplifies the port of x86_64 iommu
> > drivers to 32 bit x86 and let us get rid of pci_32.h.
> >
> > Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
>
> Would also like some more comments to explain to the kernel neophytes why
> the 32 bit version is no-op. Do other arch have same issue?
>
>
> Acked-by: Stephen Hemminger <shemminger@vyatta.com>
Ok, changed the patch description to
x86/dma: unify definition of pci_unmap_addr* and pci_unmap_len macros
Impact: unification of pci-dma macros and pci_32.h removal
This patch unifies the definition of the pci_unmap_addr*, pci_unmap_len*
and DECLARE_PCI_UNMAP* macros. This makes sense because the pci_unmap
functions are no longer no-ops anymore when the kernel runs with
CONFIG_DMA_API_DEBUG. Without an iommu or DMA_API_DEBUG it is a no-op on 32 bit
because the dma mapping path returns a physical address and therefore the
dma-api implementation has no internal state which needs to be destroyed with
an unmap call.
This unification also simplifies the port of x86_64 iommu drivers to 32 bit x86
and let us get rid of pci_32.h.
Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
Acked-by: Stephen Hemminger <shemminger@vyatta.com>
Joerg
--
| Advanced Micro Devices GmbH
Operating | Karl-Hammerschmidt-Str. 34, 85609 Dornach bei München
System |
Research | Geschäftsführer: Jochen Polster, Thomas M. McCoy, Giuliano Meroni
Center | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
| Registergericht München, HRB Nr. 43632
prev parent reply other threads:[~2009-04-02 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090401172708.GA11941@redhat.com>
2009-04-01 18:02 ` [Bug 487894] New: sky2 0000:06:00.0: DMA-API: device driver frees DMA memory with different size Stephen Hemminger
2009-04-02 10:54 ` Joerg Roedel
2009-04-02 11:06 ` FUJITA Tomonori
2009-04-02 11:18 ` Joerg Roedel
2009-04-02 14:03 ` FUJITA Tomonori
2009-04-02 14:31 ` Joerg Roedel
2009-04-02 15:08 ` Stephen Hemminger
2009-04-02 15:29 ` Joerg Roedel [this message]
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=20090402152917.GC4776@amd.com \
--to=joerg.roedel@amd.com \
--cc=davej@redhat.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=shemminger@vyatta.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox