From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752530AbeCONsV (ORCPT ); Thu, 15 Mar 2018 09:48:21 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:53509 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751788AbeCONsU (ORCPT ); Thu, 15 Mar 2018 09:48:20 -0400 Date: Thu, 15 Mar 2018 14:48:09 +0100 (CET) From: Thomas Gleixner To: Christoph Hellwig cc: x86@kernel.org, Konrad Rzeszutek Wilk , Tom Lendacky , David Woodhouse , Muli Ben-Yehuda , Jon Mason , Joerg Roedel , iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 04/14] x86: use generic swiotlb_ops In-Reply-To: <20180315133530.GA17956@lst.de> Message-ID: References: <20180314175213.20256-1-hch@lst.de> <20180314175213.20256-5-hch@lst.de> <20180315115426.GB16210@lst.de> <20180315133530.GA17956@lst.de> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 15 Mar 2018, Christoph Hellwig wrote: > On Thu, Mar 15, 2018 at 01:52:14PM +0100, Thomas Gleixner wrote: > > Yeah, I know that the standard defines it, but that doesn't mean it makes > > sense. At least not to me. > > It makes sense in that it logically is a boolean but we only want > to allocate 1 bit for it, unlike the normal ABI allocations of at > least a byte. > > Either way, tell me what you want it changed to, and I'll do it. I'd prefer either bool or a regular bitfield, but I can live with the boolean bitfield as well. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [PATCH 04/14] x86: use generic swiotlb_ops Date: Thu, 15 Mar 2018 14:48:09 +0100 (CET) Message-ID: References: <20180314175213.20256-1-hch@lst.de> <20180314175213.20256-5-hch@lst.de> <20180315115426.GB16210@lst.de> <20180315133530.GA17956@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20180315133530.GA17956-jcswGhMUV9g@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Christoph Hellwig Cc: Tom Lendacky , Konrad Rzeszutek Wilk , x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Muli Ben-Yehuda , iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, David Woodhouse List-Id: iommu@lists.linux-foundation.org On Thu, 15 Mar 2018, Christoph Hellwig wrote: > On Thu, Mar 15, 2018 at 01:52:14PM +0100, Thomas Gleixner wrote: > > Yeah, I know that the standard defines it, but that doesn't mean it makes > > sense. At least not to me. > > It makes sense in that it logically is a boolean but we only want > to allocate 1 bit for it, unlike the normal ABI allocations of at > least a byte. > > Either way, tell me what you want it changed to, and I'll do it. I'd prefer either bool or a regular bitfield, but I can live with the boolean bitfield as well.