From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from loongson.cn (mail.loongson.cn [114.242.206.163]) by sourceware.org (Postfix) with ESMTP id 2107A3858D39 for ; Tue, 27 Sep 2022 02:37:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2107A3858D39 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=loongson.cn Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=loongson.cn Received: from [10.20.4.52] (unknown [10.20.4.52]) by localhost.localdomain (Coremail) with SMTP id AQAAf8Cx72vRYTJj_Y4iAA--.60511S2; Tue, 27 Sep 2022 10:37:05 +0800 (CST) Subject: Re: [PATCH] LoongArch: Libvtv add LoongArch support. To: Xi Ruoyao , gcc-patches@gcc.gnu.org, mliska@suse.cz Cc: xuchenghua@loongson.cn, qijingwen@loongson.cn, qijingwen References: <20220926020010.779566-1-chenglulu@loongson.cn> <0c8d5a9d4aa761f8fb40ecb31cfdfdbc211891ee.camel@xry111.site> From: Lulu Cheng Message-ID: <9c34db2e-b075-f808-4120-dacbbf38539a@loongson.cn> Date: Tue, 27 Sep 2022 10:37:05 +0800 User-Agent: Mozilla/5.0 (X11; Linux mips64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <0c8d5a9d4aa761f8fb40ecb31cfdfdbc211891ee.camel@xry111.site> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-CM-TRANSID:AQAAf8Cx72vRYTJj_Y4iAA--.60511S2 X-Coremail-Antispam: 1UD129KBjvdXoWrZr17Ww4xAF1xZw18AF1DKFg_yoWfGFb_GF ZrAanrZ3WxXF4xtanxt3W2vF97K3yjkryUJF48urnrtrykJrn8GF1fu3s5JFWUKF45tw1D GrW8t3W3Gr1YgjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUbs8FF20E14v26r1j6r4UM7CY07I20VC2zVCF04k26cxKx2IYs7xG 6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rwA2F7IY1VAKz4vEj48ve4kI8w A2z4x0Y4vE2Ix0cI8IcVAFwI0_Ar0_tr1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Gr1j 6F4UJwA2z4x0Y4vEx4A2jsIE14v26r4UJVWxJr1l84ACjcxK6I8E87Iv6xkF7I0E14v26F 4UJVW0owAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40EFcxC0VAKzVAqx4xG6I80ewAv 7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r 1j6r4UM4x0Y48IcVAKI48JM4x0x7Aq67IIx4CEVc8vx2IErcIFxwCYjI0SjxkI62AI1cAE 67vIY487MxkIecxEwVCm-wCF04k20xvY0x0EwIxGrwCFx2IqxVCFs4IE7xkEbVWUJVW8Jw C20s026c02F40E14v26r1j6r18MI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAF wI0_JF0_Jw1lIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjx v20xvEc7CjxVAFwI0_Jr0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6r1j6r1xMIIF0xvEx4A2 jsIE14v26r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Jr0_GrUvcSsGvfC2KfnxnUUI43 ZEXa7VUbrMaUUUUUU== X-CM-SenderInfo: xfkh0wpoxo3qxorr0wxvrqhubq/ X-Spam-Status: No, score=-6.2 required=5.0 tests=BAYES_00,BODY_8BITS,KAM_DMARC_STATUS,NICE_REPLY_A,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: I asked my colleagues in the kernel group, this page size may change. That there is a macro BIG_PAGE_SIZE comment in vtv-change-permission.h written like this:"Replace '4096' below with correct big page size." I understand that this is to get the page size at runtime, but I don't see where this macro is used, is there something wrong with my understanding? 在 2022/9/26 下午1:38, Xi Ruoyao 写道: > On Mon, 2022-09-26 at 10:00 +0800, Lulu Cheng wrote: >> Co-Authored-By: qijingwen >> >> include/ChangeLog: >> >>         * vtv-change-permission.h (defined): >>         (VTV_PAGE_SIZE): 16k pages under loongarch64. > We have 4KB, 16KB, and 64KB page configurations, so is it possible to > support all of them without too much overhead? If not, supporting only > 16KB is OK as it's the default. >