Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp7087108imu; Mon, 21 Jan 2019 23:36:07 -0800 (PST) X-Google-Smtp-Source: ALg8bN7G5Lkxiw8lQCOdXvQ8qyUIHuk4zR4wuS9ySY8j0ShNOMbCz/9SsySO0oCKTE8wJ8hj6Ahh X-Received: by 2002:a63:cc4e:: with SMTP id q14mr30583062pgi.291.1548142567835; Mon, 21 Jan 2019 23:36:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548142567; cv=none; d=google.com; s=arc-20160816; b=SfIQj0hM87kJgNv+EcuXRKi1ycOpwE+yNXSaMAEJgfAK5ChfBkWAP8k3usMU8UJoyW 58TbOx01ABE6yqTJtsxFKrFUbW5oU03qXxmjwuKoJZcoJRs7iQdwy079Ziw2+YpG3HF7 thXW+BzBiJ+CYuw3h8X0aSHsxToYnvhYPGyNGbf9C/YHwdD4yZylMdDXcWDBUa6ZdNg4 lfYPGuDeV/+0DvwbkprVPrT5u3Gyu88az0z1S7lMzhrGSBDV1tB0pk0c+LJT4JwL44lS ztLHdzZuWqER9EP4t7MbUXKorK8GXt45X7yfXvqPTHuzTp7aLSAQdA0a6kdA7gXiEdCZ /JnQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:from:subject; bh=C//wfFy9zXd9OljvTiUbBPo+SkDv3HWWInuhK4QYBn0=; b=WXv+3pfHAmWVP/lkqk3gzBG6M/4LYCQpd3l0+EiKVaVdlFl97Ve/o1temlqKMGgw84 YwYFQ6Fqt3qsxqd7TvKJC8VeVuP8zV0xpbJ9pH1u8uBWdnOlHizcUo7LSyiwStRH/fg6 9biUVl47pcXZHabYBkS9BuBt+pyCQnZ4gBdjoT9/GQay5EMqg2NYVNn/+ERxTLk8kQwm +o434TtW0sKdMbLS7BWKsXp6sm+Imw86GlYo0dO4f7RV3Z2eJGlhN5Kqt7FonZflPT4y ZKy59uoFrjgjckS5m2eyFaEOSzjM8GssD+N3uNP2AK1N6oSaNl/+RshpINzzyEzJ7DfH 2n1g== 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 n187si14254067pfn.83.2019.01.21.23.35.52; Mon, 21 Jan 2019 23:36:07 -0800 (PST) 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 S1727313AbfAVHeM (ORCPT + 99 others); Tue, 22 Jan 2019 02:34:12 -0500 Received: from mail.cn.fujitsu.com ([183.91.158.132]:65129 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726423AbfAVHeL (ORCPT ); Tue, 22 Jan 2019 02:34:11 -0500 X-IronPort-AV: E=Sophos;i="5.56,505,1539619200"; d="scan'208";a="52559857" Received: from unknown (HELO cn.fujitsu.com) ([10.167.33.5]) by heian.cn.fujitsu.com with ESMTP; 22 Jan 2019 15:34:10 +0800 Received: from G08CNEXCHPEKD02.g08.fujitsu.local (unknown [10.167.33.83]) by cn.fujitsu.com (Postfix) with ESMTP id A91C24C4A88F; Tue, 22 Jan 2019 15:34:07 +0800 (CST) Received: from [10.167.226.60] (10.167.226.60) by G08CNEXCHPEKD02.g08.fujitsu.local (10.167.33.89) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 22 Jan 2019 15:34:08 +0800 Subject: Re: question about head_64.S From: Cao jin To: CC: Thomas Gleixner , Ingo Molnar , , "H. Peter Anvin" , LKML References: <6aebbf86-2ba1-c517-dc47-054279daec49@cn.fujitsu.com> Message-ID: <023da151-bb1d-1b11-ec1d-01eb675d528f@cn.fujitsu.com> Date: Tue, 22 Jan 2019 15:31:25 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <6aebbf86-2ba1-c517-dc47-054279daec49@cn.fujitsu.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.167.226.60] X-yoursite-MailScanner-ID: A91C24C4A88F.A7EAA X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: caoj.fnst@cn.fujitsu.com X-Spam-Status: No Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Kirll, On 1/15/19 7:45 PM, Cao jin wrote: > Hi, > I have been digging into this file for a while, and I still have 2 > questions unclear, hope to get your help. > > > 2. > Why gdt64 has following definition?: > > gdt64: > .word gdt_end - gdt > .long 0 > .word 0 > .quad 0 > > obviously, gdt64 stores the GDTR content under x86_64, which is 10 bytes > long, so why not just: > > gdt64: > .word gdt_end - gdt > .quad 0 > > With above modification, it can boot. > Seems you introduced gdt64 code in commit beebaccd50, could you help with this question? And it also remind me of another question about adjust_got which is also introduced by you. Because I failed to construct a test environment with ld version less than 2.24 until now, so I wanna do a quick ask here: does it make sense to adjust GOT from the 4th entry of it? Because as I know, the first 3 entries are special one, which (I guess) will be not used. -- Sincerely, Cao jin