public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lulu Cheng <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org, mliska@suse.cz
Cc: xuchenghua@loongson.cn, qijingwen@loongson.cn,
	qijingwen <qijingwen@rd.loongson.cn>
Subject: Re: [PATCH] LoongArch: Libvtv add LoongArch support.
Date: Tue, 27 Sep 2022 10:37:05 +0800	[thread overview]
Message-ID: <9c34db2e-b075-f808-4120-dacbbf38539a@loongson.cn> (raw)
In-Reply-To: <0c8d5a9d4aa761f8fb40ecb31cfdfdbc211891ee.camel@xry111.site>

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 <qijingwen@rd.loongson.cn>
>>
>> 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.
>


  reply	other threads:[~2022-09-27  2:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26  2:00 Lulu Cheng
2022-09-26  5:38 ` Xi Ruoyao
2022-09-27  2:37   ` Lulu Cheng [this message]
2022-09-27  3:08     ` Xi Ruoyao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9c34db2e-b075-f808-4120-dacbbf38539a@loongson.cn \
    --to=chenglulu@loongson.cn \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mliska@suse.cz \
    --cc=qijingwen@loongson.cn \
    --cc=qijingwen@rd.loongson.cn \
    --cc=xry111@xry111.site \
    --cc=xuchenghua@loongson.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).