From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
herbert@gondor.apana.org.au, neilb@suse.de,
schwidefsky@de.ibm.com, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: crypto/async_tx/* doesn't build on s390
Date: Sun, 3 Feb 2008 12:40:57 +0100 [thread overview]
Message-ID: <20080203114056.GB18211@osiris.ibm.com> (raw)
In-Reply-To: <e9c3a7c20802011331j2064afe5vc6228fe8363e15de@mail.gmail.com>
On Fri, Feb 01, 2008 at 02:31:28PM -0700, Dan Williams wrote:
> On Feb 1, 2008 4:37 AM, Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> > On Thu, 31 Jan 2008 12:49:00 -0700,
> > "Williams, Dan J" <dan.j.williams@intel.com> wrote:
> >
> > > I am mistaken, the 'depends on ARCH...' precludes HAS_DMA. Perhaps the compiler is emitting a call to async_tx_find_channel when it needs to be inline? On x86 do_async_xor is successfully compiled away when CONFIG_DMA_ENGINE=n.
> >
> > Just checked why it compiled for me on one box but not on the other and
> > found that deactivating CONFIG_SECTION_MISMATCH makes it go away. Hmm...
> >
>
> Here is what I have come up with as a fix.
The fix works for me. Thanks! However your mailer replaced tabs with spaces
and added an extra line break.
> ---
> async_tx: prevent do_async_xor from compiling on !HAS_DMA archs
>
> With the addition of -fno-inline in CONFIG_DEBUG_SECTION_MISMATCH
> do_async_xor is no longer compiled away on !HAS_DMA archs like s390.
> Other async_tx calls to the dma-api are already open coded inline.
>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> ---
>
> crypto/async_tx/async_xor.c | 8 ++++++++
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
>
> diff --git a/crypto/async_tx/async_xor.c b/crypto/async_tx/async_xor.c
> index 2575f67..393f07d 100644
> --- a/crypto/async_tx/async_xor.c
> +++ b/crypto/async_tx/async_xor.c
> @@ -41,6 +41,14 @@ do_async_xor(struct dma_async_tx_descriptor *tx,
> struct dma_device *device,
> enum dma_data_direction dir;
> int i;
>
> + /* if this function is not inlined we need to prevent
> + * the rest of the routine from compiling on !HAS_DMA
> + * archs
> + */
> + #ifndef CONFIG_DMA_ENGINE
> + return;
> + #endif
> +
> pr_debug("%s: len: %zu\n", __FUNCTION__, len);
>
> dir = (flags & ASYNC_TX_ASSUME_COHERENT) ?
next prev parent reply other threads:[~2008-02-03 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0C7297FA1D2D244A9C7F6959C0BF1E521D1C6C@azsmsx413.amr.corp.intel.com>
2008-02-01 11:37 ` Cornelia Huck
2008-02-01 21:31 ` Dan Williams
2008-02-03 11:40 ` Heiko Carstens [this message]
2008-02-03 14:10 ` Dan Williams
2008-02-04 11:48 ` Cornelia Huck
2008-01-31 14:50 Heiko Carstens
2008-01-31 17:26 ` Cornelia Huck
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=20080203114056.GB18211@osiris.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cornelia.huck@de.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=schwidefsky@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®