From: Xi Ruoyao <xry111@xry111.site>
To: Lulu Cheng <chenglulu@loongson.cn>,
gcc-patches@gcc.gnu.org, mliska@suse.cz
Cc: xuchenghua@loongson.cn, qijingwen@loongson.cn,
qijingwen <qijingwen@rd.loongson.cn>,
Caroline Tice <cmtice@google.com>
Subject: Re: [PATCH] LoongArch: Libvtv add LoongArch support.
Date: Tue, 27 Sep 2022 11:08:52 +0800 [thread overview]
Message-ID: <67f6c8084d545b6fe433fedcd3f54c25b57e9fe3.camel@xry111.site> (raw)
In-Reply-To: <9c34db2e-b075-f808-4120-dacbbf38539a@loongson.cn>
+ Caroline (the author or libvtv, I hope the email address is still
active).
On Tue, 2022-09-27 at 10:37 +0800, Lulu Cheng wrote:
> 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?
Frankly, I've never used libvtv (Linux From Scratch does not --enable-
vtable-verify). But if I understand correctly, we can set "65536" here
and *I guess* the result will be able to function on 4/16/64 KB pages
(but with some performance overhead on 4/16 KB).
"BIG_PAGE_SIZE" seems not defined anywhere in GCC...
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2022-09-27 3:08 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
2022-09-27 3:08 ` Xi Ruoyao [this message]
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=67f6c8084d545b6fe433fedcd3f54c25b57e9fe3.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenglulu@loongson.cn \
--cc=cmtice@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
--cc=qijingwen@loongson.cn \
--cc=qijingwen@rd.loongson.cn \
--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).