From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Tong Tiangen <tongtiangen@huawei.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmerdabbelt@google.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, <abdulras@google.com>
Cc: <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next v3 0/3] riscv: Fix two vdso issue
Date: Wed, 29 Sep 2021 18:12:38 +0800 [thread overview]
Message-ID: <37778b13-aa03-c885-f78c-da50ac9fa602@huawei.com> (raw)
In-Reply-To: <20210901024621.2528797-1-tongtiangen@huawei.com>
Hi Palmer, could this patchset be merged into v5.15, it fixes the
serious problems about the basic time api.
Sergey[1] does meet same issue too. Thanks.
[1]
https://patchwork.kernel.org/project/linux-riscv/patch/20210829094708.169037-1-cerg2010cerg2010@mail.ru/
On 2021/9/1 10:46, Tong Tiangen wrote:
> v3->v2:
> Adapt to the latest code.
>
> v2->v1:
> Add patch "Refactor asm/vdso.h" to avoid vdso.lds syntax error if
> CONFIG_GENERIC_TIME_VSYSCALL=n.
>
> 1) Move vdso data page up front and introduce enum vvar_pages, This makes it
> easier to introduce new feature TIME_NS.
>
> 2) In arch_setup_additional_pages(), make Wait for the lock in the killable mode
> and return with EINTR if the task got killed while waiting.
Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei.com>
next prev parent reply other threads:[~2021-09-29 10:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 2:46 Tong Tiangen
2021-09-01 2:46 ` [PATCH -next v3 1/3] riscv/vdso: Refactor asm/vdso.h Tong Tiangen
2021-09-01 2:46 ` [PATCH -next v3 2/3] riscv/vdso: Move vdso data page up front Tong Tiangen
2021-09-01 2:46 ` [PATCH -next v3 3/3] riscv/vdso: make arch_setup_additional_pages wait for mmap_sem for write killable Tong Tiangen
2021-09-28 2:19 ` [PATCH -next v3 0/3] riscv: Fix two vdso issue Liu Shixin
2021-09-28 2:30 ` tongtiangen
2021-09-29 10:12 ` Kefeng Wang [this message]
2021-10-02 20:24 ` Palmer Dabbelt
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=37778b13-aa03-c885-f78c-da50ac9fa602@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=abdulras@google.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmerdabbelt@google.com \
--cc=paul.walmsley@sifive.com \
--cc=tongtiangen@huawei.com \
/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
all inboxes | Powered by JetHome®