public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Rubini <rubini@gnudd.com>
To: konrad.wilk@oracle.com
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	linux-ia64@vger.kernel.org, linux-mips@linux-mips.org,
	giancarlo.asnaghi@st.com, tony.luck@intel.com,
	fenghua.yu@intel.com, ralf@linux-mips.org, gxt@mprc.pku.edu.cn,
	tglx@linutronix.de, kyungmin.park@samsung.com,
	fujita.tomonori@lab.ntt.co.jp
Subject: Re: [PATCH] swiotlb: add "dma_attrs" argument to alloc and free, to match dma_map_ops
Date: Thu, 24 May 2012 20:53:25 +0200	[thread overview]
Message-ID: <20120524185325.GA16292@mail.gnudd.com> (raw)
In-Reply-To: <20120524174741.GG24934@phenom.dumpdata.com>

>> The alloc and free pointers within "struct dma_map_ops" receive a
>> pointer to dma_attrs that was not present in the generic swiotlb
>> functions.  For this reason, a few files had a local wrapper for the
>> free function that just removes the attrs argument before calling the
>> generic function.
>> 
>> This patch adds the extra argument to generic functions and removes
>> such wrappers when they are no more needed.  This also fixes a
>> compiler warning for sta2x11-fixup.c, that would have required yet
>> another wrapper.

> So .. what is this based on?

Current linux-next. But it has been like this for a while. I had
the warning in sta2x11-fixup.c pending for a while, and yesterday
I raised the issue.

> I see in mainline  alloc_coherent and free_coherent
> which are obviously changed here.

Do you refer to the swiotlb methods (I confirm they are changed, like
all their users) or something else? I'm only changing the two methods
in swiotlb, nothing else is affected.

Actually, I wanted to call them alloc and free, like the field they
are assigned to, but swiotlb_free is already there, to do something
else.
 
> Don't you also need to change these two files:
> 
>  arch/x86/xen/pci-swiotlb-xen.c
>  drivers/xen/swiotlb-xen.c

No, because xen implements the dma_map_ops with the proper prototypes.
I grepped for all users, and found these are not related.

Thank your for checking
/alessandro

      reply	other threads:[~2012-05-24 18:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 11:44 [PATCH] swiotlb: add "dma_attrs" argument to alloc and free, to match dma_map_ops Alessandro Rubini
2012-05-24 15:15 ` David Daney
2012-05-24 17:47 ` Konrad Rzeszutek Wilk
2012-05-24 18:53   ` Alessandro Rubini [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=20120524185325.GA16292@mail.gnudd.com \
    --to=rubini@gnudd.com \
    --cc=fenghua.yu@intel.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=giancarlo.asnaghi@st.com \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=konrad.wilk@oracle.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox