From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 41F67C31E46 for ; Wed, 12 Jun 2019 13:14:31 +0000 (UTC) Received: from mail.linuxfoundation.org (mail.linuxfoundation.org [140.211.169.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 182A420874 for ; Wed, 12 Jun 2019 13:14:31 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 182A420874 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=8bytes.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=iommu-bounces@lists.linux-foundation.org Received: from mail.linux-foundation.org (localhost [127.0.0.1]) by mail.linuxfoundation.org (Postfix) with ESMTP id DA12F1C3C; Wed, 12 Jun 2019 13:14:30 +0000 (UTC) Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id D18001C33 for ; Wed, 12 Jun 2019 13:11:46 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from theia.8bytes.org (8bytes.org [81.169.241.247]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9C91E79 for ; Wed, 12 Jun 2019 13:11:45 +0000 (UTC) Received: by theia.8bytes.org (Postfix, from userid 1000) id 9C2EF64D; Wed, 12 Jun 2019 15:11:43 +0200 (CEST) Date: Wed, 12 Jun 2019 15:11:43 +0200 From: Joerg Roedel To: Jean-Philippe Brucker Subject: Re: [PATCH v2 0/4] iommu: Add device fault reporting API Message-ID: <20190612131143.GF21613@8bytes.org> References: <20190603145749.46347-1-jean-philippe.brucker@arm.com> <20190612081944.GB17505@8bytes.org> <0f21e1b2-837f-87ba-6cf3-f6490d9e2a57@arm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <0f21e1b2-837f-87ba-6cf3-f6490d9e2a57@arm.com> User-Agent: Mutt/1.9.4 (2018-02-28) Cc: "ashok.raj@intel.com" , "iommu@lists.linux-foundation.org" , "linux-kernel@vger.kernel.org" , "alex.williamson@redhat.com" , Robin Murphy X-BeenThere: iommu@lists.linux-foundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Development issues for Linux IOMMU support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: iommu-bounces@lists.linux-foundation.org Errors-To: iommu-bounces@lists.linux-foundation.org On Wed, Jun 12, 2019 at 12:54:51PM +0100, Jean-Philippe Brucker wrote: > Thanks! As discussed I think we need to add padding into the iommu_fault > structure before this reaches mainline, to make the UAPI easier to > extend in the future. It's already possible to extend but requires > introducing a new ABI version number and support two structures. Adding > some padding would only require introducing new flags. If there is no > objection I'll send a one-line patch bumping the structure size to 64 > bytes (currently 48) Sounds good, please submit the patch. Regards, Joerg _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu