Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1557922yba; Sat, 27 Apr 2019 02:01:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqyM9isUPCmkIVAjkEitFqcxD5JxVTRyHqG9mus+yVy+pv62+rxJxB4FYlynf3YzPn7jQCTT X-Received: by 2002:a62:3892:: with SMTP id f140mr51382555pfa.128.1556355668213; Sat, 27 Apr 2019 02:01:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556355668; cv=none; d=google.com; s=arc-20160816; b=bS1bPrKFagLajP5M2vJk9IcOIqUcswBcdVwtZUEaS40qY2irEEKQi+W2rpuwo5QCVr yDAdolyNFBoO417WFYZAQRVsYRPmxxMCzIAOafZ8gboUO2buG/jLSpJtStMV/VlpPYVT RmDLxtRiCTT3Xim9MRJvh6KQC9p4UckIr9cVbS2wD10hLOf0gmMLEH2L1O1Q8fBKkxAn HKnUBCz6eixg9DGXGiCBfAGSe2Vqx8/nUUTTP8FQwjUDbx3xxtfbXht7bigzPhJE3/uV NDh+mioib1dz2v2pBxjyAjGN/ODiYWElW9D6JujeDAazt05FNtGPCfN9koqqlfnwLk2E 32vg== 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-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=kqxj+Mb+avwOQkG2QpygoX7fctHS9uCBxZi/TSKRP+M=; b=f+zgilJRgfGw+U8KkI+3HRLR3Ar7lpZY73R1i7UsILq3RoZ+afR0gYnURIwgE+bAyO tmsSH4A+9yh3rbFF60Pi2dRGsoMt2QrOrL17pu1ZdKoInaIGeUTm41bQz94xjfVPTEDH YbGQI2iBhTH+G1egEXbrRkNMWeyb+uEPEksZXd4pXIhfDfwnPBT939xGRJzL+SxDz2Kh iCBTJLwXJji5wuJDox1j8dNHPMY0oivTlKDFcVQxuE1tZ7pAcQvId6oZHbhjNvLCdo8q uheX3M5KWA1hakSy9q5Q4mPkSpRujaSPa5KyBnpzGXm/Q7dzWl78ay26Qyq0DTdroqt3 uPOQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@alien8.de header.s=dkim header.b="HMmIcA1/"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=alien8.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 64si17496565plb.303.2019.04.27.02.00.43; Sat, 27 Apr 2019 02:01:08 -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; dkim=pass header.i=@alien8.de header.s=dkim header.b="HMmIcA1/"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=alien8.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725996AbfD0I6V (ORCPT + 99 others); Sat, 27 Apr 2019 04:58:21 -0400 Received: from mail.skyhub.de ([5.9.137.197]:59430 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725857AbfD0I6V (ORCPT ); Sat, 27 Apr 2019 04:58:21 -0400 Received: from zn.tnic (p200300EC2F1D42004591EACC18991034.dip0.t-ipconnect.de [IPv6:2003:ec:2f1d:4200:4591:eacc:1899:1034]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 77F561EC027B; Sat, 27 Apr 2019 10:58:20 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1556355500; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=kqxj+Mb+avwOQkG2QpygoX7fctHS9uCBxZi/TSKRP+M=; b=HMmIcA1/wBf8K64aGvoCsy+3a8Ez+f4/9wUVP8diYjy00VTiHdNTFCSCaCQvqmacwgLN/8 0smEMop76TOlb63HOhdvVAAlcU6BB1Uu0+98PXTBq3bbZ1g32G6Wi/UdODmSnfcdgIYh7q La1vB8W0n5qxUFQ2t2cI+fHrOuPiVJY= Date: Sat, 27 Apr 2019 10:58:16 +0200 From: Borislav Petkov To: "Zhao, Yakui" Cc: Ingo Molnar , "linux-kernel@vger.kernel.org" , "x86@kernel.org" , "tglx@linutronix.de" , "Chen, Jason CJ" Subject: Re: [RFC PATCH v5 4/4] x86/acrn: Add hypercall for ACRN guest Message-ID: <20190427085816.GB12360@zn.tnic> References: <1556067260-9128-1-git-send-email-yakui.zhao@intel.com> <1556067260-9128-5-git-send-email-yakui.zhao@intel.com> <20190425070712.GA57256@gmail.com> <6dd021a9-e2c0-ee84-55fd-3e6dfb4bd944@intel.com> <20190425110025.GA16164@zn.tnic> <473d145c-4bfd-4ec8-34c3-8a26a78fe40d@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <473d145c-4bfd-4ec8-34c3-8a26a78fe40d@intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 26, 2019 at 11:18:48AM +0800, Zhao, Yakui wrote: > It seems that it is seldom used in kernel although the explicit register > variable is supported by GCC and makes the code look simpler. And it seems > that the explicit register variable is not suppoorted by CLAG. The more reason not to do it this way. Also, the "register" variable specification is not very widespread in x86 when you look at $ git grep -E "register\s.*asm" arch/x86/ output. > So the explicit register variable will be removed. I will follow the asm > code from Borislav. Of course one minor change is that the "movq" is used > instead of "mov". Does that matter if your destination register is 64-bit? -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.