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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 2F309E784A9 for ; Thu, 5 Oct 2023 06:27:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=6VjtCuwAXjMw28YNcFR/HV+uIEewZmOaVAJFFjHFToY=; b=q8s23DgofQIOnJ Ge6Pl+DK5aQBvVML8MLwI51E5sJXqhi8qxDfhVgrw2CGxp1+MoDjXWxRCdsZBq8b6AzUI1Myj6qB/ KzVcmHDzd6ti4dyhBSzbslPk0KdqHoxsacz59USn2oQMQYJPwZaBVj9z4mFkv3lRQMcfx47+uFr3q nuaLnz4N/odQ3MuqaAHWlnIToIpWm1cTuLem+5PQX81NW+WG18eYJ2pIRZnzlGR4YNNX5zbw1optq 6yz0qC/t6GZO2WGcD8MtN0IejMnfndVQ/DcqX4svdtGOk37F2pRWgx3xUKR5QajjAB2VQHEUC7j/V Ob9FnyVTP6TNZweRU6xw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qoHow-001W93-0u; Thu, 05 Oct 2023 06:26:50 +0000 Received: from ams.source.kernel.org ([145.40.68.75]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qoHos-001W84-0S for linux-arm-kernel@lists.infradead.org; Thu, 05 Oct 2023 06:26:48 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by ams.source.kernel.org (Postfix) with ESMTP id CCD85B8225C; Thu, 5 Oct 2023 06:26:41 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5D80EC433AD; Thu, 5 Oct 2023 06:26:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1696487200; bh=9xyNVyN7N7MBzA9UwuP9xPWMA9I3taWkS2jqsvKhr3s=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jLcSNkQ/LCUGlX23x7bKHMrm6O+lCfLyVyl4lJFpqj9ZiSYYzwxEp9jZma31Pfllr wdUrN6biBfOS5V6bMBNu6EAM0Sq3HUrUansreS7bmBd3mLFduc2pF/kqcY06+yQC5z D87SMtm/bM/1USoOdPqeLZaEubagHNYsjEKm7koc= Date: Thu, 5 Oct 2023 08:26:38 +0200 From: Greg KH To: Nuno Das Neves Cc: Dexuan Cui , Wei Liu , "linux-hyperv@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "x86@kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-arch@vger.kernel.org" , "patches@lists.linux.dev" , "Michael Kelley (LINUX)" , KY Srinivasan , Haiyang Zhang , "apais@linux.microsoft.com" , Tianyu Lan , "ssengar@linux.microsoft.com" , MUKESH RATHOR , "stanislav.kinsburskiy@gmail.com" , "jinankjain@linux.microsoft.com" , vkuznets , "tglx@linutronix.de" , "mingo@redhat.com" , "bp@alien8.de" , "dave.hansen@linux.intel.com" , "hpa@zytor.com" , "will@kernel.org" , "catalin.marinas@arm.com" Subject: Re: [PATCH v4 13/15] uapi: hyperv: Add mshv driver headers defining hypervisor ABIs Message-ID: <2023100540-linked-remote-3da7@gregkh> References: <1696010501-24584-1-git-send-email-nunodasneves@linux.microsoft.com> <1696010501-24584-14-git-send-email-nunodasneves@linux.microsoft.com> <2023093057-eggplant-reshoot-8513@gregkh> <2023100154-ferret-rift-acef@gregkh> <2023100443-wrinkly-romp-79d9@gregkh> <2023100415-diving-clapper-a2a7@gregkh> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231004_232646_485734_825B6766 X-CRM114-Status: GOOD ( 37.22 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Oct 04, 2023 at 11:16:46AM -0700, Nuno Das Neves wrote: > On 10/4/2023 10:50 AM, Greg KH wrote: > > On Wed, Oct 04, 2023 at 05:36:32PM +0000, Dexuan Cui wrote: > > > > From: Greg KH > > > > Sent: Tuesday, October 3, 2023 11:10 PM > > > > [...] > > > > On Tue, Oct 03, 2023 at 04:37:01PM -0700, Nuno Das Neves wrote: > > > > > On 9/30/2023 11:19 PM, Greg KH wrote: > > > > > > On Sat, Sep 30, 2023 at 10:01:58PM +0000, Wei Liu wrote: > > > > > > > On Sat, Sep 30, 2023 at 08:09:19AM +0200, Greg KH wrote: > > > > > > > > On Fri, Sep 29, 2023 at 11:01:39AM -0700, Nuno Das Neves wrote: > > > > > > > > > +/* Define connection identifier type. */ > > > > > > > > > +union hv_connection_id { > > > > > > > > > + __u32 asu32; > > > > > > > > > + struct { > > > > > > > > > + __u32 id:24; > > > > > > > > > + __u32 reserved:8; > > > > > > > > > + } __packed u; > > > > > > IMO the "__packed" is unnecessary. > > > > > > > > > > > bitfields will not work properly in uapi .h files, please never do that. > > > > > > > > > > > > > > Can you clarify a bit more why it wouldn't work? Endianess? Alignment? > > > > > > > > > > > > Yes to both. > > > > > > > > > > > > Did you all read the documentation for how to write a kernel api? If > > > > > > not, please do so. I think it mentions bitfields, but it not, it really > > > > > > should as of course, this will not work properly with different endian > > > > > > systems or many compilers. > > > > > > > > > > Yes, in > > > > https://docs.k/ > > > > ernel.org%2Fdriver- > > > > api%2Fioctl.html&data=05%7C01%7Cdecui%40microsoft.com%7Ce404769e0f > > > > 85493f0aa108dbc4a08a27%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C > > > > 0%7C638319966071263290%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLj > > > > AwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C% > > > > 7C%7C&sdata=RiLNA5DRviWBQK6XXhxC4m77raSDBb%2F0BB6BDpFPUJY%3D > > > > &reserved=0 it says that it is > > > > > "better to avoid" bitfields. > > > > > > > > > > Unfortunately bitfields are used in the definition of the hypervisor > > > > > ABI. We import these definitions directly from the hypervisor code. > > > > > > > > So why do you feel you have to use this specific format for your > > > > user/kernel api? That is not what is going to the hypervisor. > > > > These *are* going to the hypervisor - we use these same definitions in > our driver for the kernel/hypervisor API. This is so we don't have to > maintain two separate definitions for user/kernel and kernel/hypervisor > APIs. So these fields are just pass-through from userspace to the hypervisor and are not touched at all by the kernel? If so, I hope the hypervisor is doing some validation of the data :) > > > If it's hard to avoid bitfield here, maybe we can refer to the definition of > > > struct iphdr in include/uapi/linux/ip.h > > > > It is not hard to avoid using bitfields, just use the proper definitions > > to make this portable for all compilers. And ick, ip.h is not a good > > thing to follow :) > > > Greg, there is nothing making us use bitfields. It just makes the work > of porting the hypervisor definitions to Linux easier - aided by the > fact that in practice, all the compilers in our stack produce the same > code for these. "our stack" is not how Linux works, you have to write files that work for all compilers here. Just use a normal variable and define the bits in them with proper bit shifts or masks and that will be portable everywhere. This isn't rocket science... thanks, greg k-h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel