linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Burton <paulburton@kernel.org>
To: Guoyun Sun <sunguoyun@loongson.cn>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Paul Burton <paulburton@kernel.org>,
	Allison Randal <allison@lohutok.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	Guoyun Sun <sunguoyun@loongson.cn>
Cc: linux-mips@vger.kernel.org
Subject: Re: [PATCH V2] mips/vdso: Support mremap() for vDSO
Date: Wed, 15 Jan 2020 10:59:22 -0800	[thread overview]
Message-ID: <5e1f610b.1c69fb81.f82c3.5b13@mx.google.com> (raw)
In-Reply-To: <1579059300-6636-1-git-send-email-sunguoyun@loongson.cn>

Hello,

Guoyun Sun wrote:
> vDSO VMA address is saved in mm_context for the purpose of using
> restorer from vDSO page to return to userspace after signal handling.
> 
> In Checkpoint Restore in Userspace (CRIU) project we place vDSO VMA
> on restore back to the place where it was on the dump.
> 
> Make vDSO code track the VMA address by supplying .mremap() fops
> the same way it's done for x86 and arm by:
> commit b059a453b1cf ("x86/vdso: Add mremap hook to vm_special_mapping")
> commit 739586951b8a ("arm64/vdso: Support mremap() for vDSO").

Applied to mips-next.

> commit ad1df95419cc
> https://git.kernel.org/mips/c/ad1df95419cc
> 
> Signed-off-by: Guoyun Sun <sunguoyun@loongson.cn>
> Signed-off-by: Paul Burton <paulburton@kernel.org>

Thanks,
    Paul

[ This message was auto-generated; if you believe anything is incorrect
  then please email paulburton@kernel.org to report it. ]

      reply	other threads:[~2020-01-15 18:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15  3:35 [PATCH V2] mips/vdso: Support mremap() for vDSO Guoyun Sun
2020-01-15 18:59 ` Paul Burton [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=5e1f610b.1c69fb81.f82c3.5b13@mx.google.com \
    --to=paulburton@kernel.org \
    --cc=allison@lohutok.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=ralf@linux-mips.org \
    --cc=sunguoyun@loongson.cn \
    --cc=tglx@linutronix.de \
    /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 NNTP newsgroup(s).