LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Tong Tiangen <tongtiangen@huawei.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	"Palmer Dabbelt" <palmerdabbelt@google.com>,
	Albert Ou <aou@eecs.berkeley.edu>
Cc: <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next 0/2] riscv: Fix two vdso issue
Date: Thu, 19 Aug 2021 13:24:24 +0800	[thread overview]
Message-ID: <7b9520dd-1c61-4a5f-7239-b42f5f37cb54@huawei.com> (raw)
In-Reply-To: <20210819030650.716478-1-tongtiangen@huawei.com>

On 2021/8/19 11:06, Tong Tiangen wrote:
> 1) Move vdso data page up front and introduce enum vvar_pages, To pave the way
> for the subsequent support of TIME_NS, the support of TIME_NS will be issued
> in the later patch.
>
> 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.

For series,

Reviewed-by: Kefeng Wang <wangkefeng.wang@huawei.com>

>
> Tong Tiangen (2):
>    riscv/vdso: Move vdso data page up front
>    riscv/vdso: make arch_setup_additional_pages wait for mmap_sem for
>      write killable
>
>   arch/riscv/include/asm/syscall.h  |  2 ++
>   arch/riscv/include/asm/vdso.h     |  4 +--
>   arch/riscv/kernel/vdso.c          | 51 ++++++++++++++++++-------------
>   arch/riscv/kernel/vdso/vdso.lds.S |  3 +-
>   4 files changed, 36 insertions(+), 24 deletions(-)
>

      parent reply	other threads:[~2021-08-19  5:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19  3:06 Tong Tiangen
2021-08-19  3:06 ` [PATCH -next 1/2] riscv/vdso: Move vdso data page up front Tong Tiangen
2021-08-19  9:43   ` kernel test robot
2021-08-19  3:06 ` [PATCH -next 2/2] riscv/vdso: make arch_setup_additional_pages wait for mmap_sem for write killable Tong Tiangen
2021-08-19  5:24 ` Kefeng Wang [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=7b9520dd-1c61-4a5f-7239-b42f5f37cb54@huawei.com \
    --to=wangkefeng.wang@huawei.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 \
    --subject='Re: [PATCH -next 0/2] riscv: Fix two vdso issue' \
    /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

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 NNTP newsgroup(s).