From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932484AbeC0QpJ (ORCPT ); Tue, 27 Mar 2018 12:45:09 -0400 Received: from verein.lst.de ([213.95.11.211]:41324 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755713AbeC0QpH (ORCPT ); Tue, 27 Mar 2018 12:45:07 -0400 Date: Tue, 27 Mar 2018 18:45:05 +0200 From: Christoph Hellwig To: Sebastian Ott Cc: Christoph Hellwig , Jesper Nilsson , Geert Uytterhoeven , linux-kernel@vger.kernel.org Subject: Re: dma_zalloc_coherent broken with 57bf5a8963f80fb3828c46c3e3a5b2dd790e09a7 Message-ID: <20180327164505.GA10522@lst.de> References: <20180327143341.GA4968@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 27, 2018 at 05:24:10PM +0200, Sebastian Ott wrote: > What do you mean by current implementations? Arch specific code? At least > on s390 we don't do that. dma-mapping.h doesn't do it either. The arch implementations should do it. Seems like s390 and potentially a few others don't. I'm a little slow due to a cast on one arm, but I'll do an audit and will fix up anything I'll find.