Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp8398806ybn; Tue, 1 Oct 2019 07:36:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqwuTtr3FBneJ0SMVyIOVKTQwr5qZjRhmhms0MrQIsSoyJhYesvHe32HQ0sTenbh3xFQXvcn X-Received: by 2002:a17:906:1f89:: with SMTP id t9mr11011781ejr.241.1569940567055; Tue, 01 Oct 2019 07:36:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569940567; cv=none; d=google.com; s=arc-20160816; b=LWz9Nvt0IQKNGAczEY/7vSn2OqlTSLHclFN+7IrEobk/jcm/hp+VDgY37haTdpw7HK HypVIX4NqSmiHOpXfIuj16Ki1s9AeE9srSf5oFHZR6wNd/hsTDwJ2UM8u7BQ5Ng5rl6W KOm9NN840L0lO1Cy7pGLF0jlJoa0BnJQhm7NjfSSJjMeWjlRGex+U0NDZCkrgjb9gEar X0O4tNU9GLKx7JPrllp4w5Sm9C4R85jWNTfVBq0M7lUCnvrStmdFIDylOLG9VBRsXnWR d4ZHDVnVn9ebUuBFtV4N5Z4TTVCu4t2aRkc2dfpp1H/GPJHevmuF9Dl3NKQYsCRrPcXc 8lPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=Oy3ZITST5LQNjSFrkDihKGEujnz0/bo8MARQaU8Gfwk=; b=nfoh+TdBEWIs59amgW3/9Yylbz1dj9hiFcJkHIR1F9YjTbrd42QAo4cEsXiZQ7Yr+x Dp7dna/vqaqLbHhYxaFxQGx8BKLSYvrQzSm1MqhoZ2q5kH/yCBdIi44KyORYoJ26Dip3 5272gGBP1zF9XmyrEiTVC/EYHmZqqjaWRVvj/WBG5zZZpM6CLap5qnnXb1GL78jZU/8/ NZLKsbdBBNsvZsxjDc5MjyuaJLBUNQFDrCRpMtR3cSJnP2q5Cc+IgRCZTRVvZV+KD874 DyyELzABiEXsE5MiTd5ee0enn4GoLHAOLtCT3Ti8nuOpAC8Mw+mBbjJ+6c5eUcEhFhOa CYoA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a7si1203646ejy.131.2019.10.01.07.35.41; Tue, 01 Oct 2019 07:36:07 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388891AbfJAOeH (ORCPT + 99 others); Tue, 1 Oct 2019 10:34:07 -0400 Received: from foss.arm.com ([217.140.110.172]:51036 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727055AbfJAOeG (ORCPT ); Tue, 1 Oct 2019 10:34:06 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id EFD9A1000; Tue, 1 Oct 2019 07:34:05 -0700 (PDT) Received: from lakrids.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 63D533F71A; Tue, 1 Oct 2019 07:34:04 -0700 (PDT) Date: Tue, 1 Oct 2019 15:33:43 +0100 From: Mark Rutland To: Julien Grall Cc: Andrew Cooper , Arnd Bergmann , Stefano Stabellini , Emil Velikov , Russell King , Denis Efremov , "linux-kernel@vger.kernel.org" , Masahiro Yamada , xen-devel , Linux ARM , Will Deacon Subject: Re: [Xen-devel] [PATCH] ARM: xen: unexport HYPERVISOR_platform_op function Message-ID: <20191001143334.GA46651@lakrids.cambridge.arm.com> References: <20190906153948.2160342-1-arnd@arndb.de> <7abad95e-ea47-c068-d91c-ba503f2530b9@citrix.com> <95dbd972-fe78-d0ca-f7b4-1a6bdd418eab@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <95dbd972-fe78-d0ca-f7b4-1a6bdd418eab@arm.com> User-Agent: Mutt/1.11.1+11 (2f07cb52) (2018-12-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Julien, On Sat, Sep 07, 2019 at 11:05:45AM +0100, Julien Grall wrote: > On 9/6/19 6:20 PM, Andrew Cooper wrote: > > On 06/09/2019 17:00, Arnd Bergmann wrote: > > > On Fri, Sep 6, 2019 at 5:55 PM Andrew Cooper wrote: > > > > On 06/09/2019 16:39, Arnd Bergmann wrote: > > > > > HYPERVISOR_platform_op() is an inline function and should not > > > > > be exported. Since commit 15bfc2348d54 ("modpost: check for > > > > > static EXPORT_SYMBOL* functions"), this causes a warning: > > > > > > > > > > WARNING: "HYPERVISOR_platform_op" [vmlinux] is a static EXPORT_SYMBOL_GPL > > > > > > > > > > Remove the extraneous export. > > > > > > > > > > Fixes: 15bfc2348d54 ("modpost: check for static EXPORT_SYMBOL* functions") > > > > > Signed-off-by: Arnd Bergmann > > > > Something is wonky. That symbol is (/ really ought to be) in the > > > > hypercall page and most definitely not inline. > > > > > > > > Which tree is that changeset from? I can't find the SHA. > > > This is from linux-next, I think from the kbuild tree. > > > > Thanks. > > > > Julien/Stefano: Why are any of these hypercalls out-of-line?  ARM > > doesn't use the hypercall page, and there is no argument translation > > (not even in arm32 as there are no 5-argument hypercalls declared). > > I am not sure how the hypercall page makes things different. You still have > to store the arguments in the correct register so... > > > > > They'd surely be easier to implement with a few static inlines and some > > common code, than to try and replicate the x86 side hypercall_page > > interface ? > > ... I don't think they will be easier to implement with a few static > inlines. The implementation will likely end up to be similar to > arch/x86/asm/xen/hypercall.h. > > Furthermore, one of the downside of per-arch static inline is it is more > difficult to ensure the prototype match for all the architectures. Although, > it might be possible to make them common by only requesting per-arch to > implement HYPERCALL_N(...). > > So I think the code is better as it is. > > While looking at the code, I also realized that the implementation of > HYPERCALL_dm_op might be incorrect for Arm32. Similarly do privcmd call, I > think dm_op call should enable user access as they will be used by > userspace. > > We don't use dm_op on Arm so far, hence why I think this was unnoticed. I > will see if I can reproduce it and send a patch. I'm seeing this when building arm64 defconfig v5.4-rc1: | [mark@lakrids:~/src/linux]% usekorg 8.1.0 make ARCH=arm64 CROSS_COMPILE=aarch64-linux- -j56 -s | arch/arm64/Makefile:62: CROSS_COMPILE_COMPAT not defined or empty, the compat vDSO will not be built | WARNING: "HYPERVISOR_platform_op" [vmlinux] is a static EXPORT_SYMBOL_GPL | WARNING: "HYPERVISOR_platform_op" [vmlinux] is a static EXPORT_SYMBOL_GPL I couldn't see a follow-up; do you have a patch for this? Thanks, Mark.