From: nfortino@nvidia.com (Nickolas Fortino)
To: linux-arm-kernel@lists.infradead.org
Subject: preempted dup_mm misses TLB invalidate
Date: Wed, 17 Jul 2013 18:48:37 -0700 [thread overview]
Message-ID: <51E74975.9040105@nvidia.com> (raw)
In-Reply-To: <20130717212148.GV24642@n2100.arm.linux.org.uk>
On 7/17/2013 2:21 PM, Russell King - ARM Linux wrote:
> I'm
> willing to bet that the behaviour you observe on ARM is inherently visible
> on many of the other Linux architectures.
Based on the discussion from this thread, I agree there is nothing
architecture specific here. This behavior also appears legal, so long as
any page with write permissions in the TLB is considered dirty in the
linux PTE structure.
I had missed the specification for fork() is silent on what happens to
MAP_PRIVATE memory modifications which occur during the execution of
fork(); it merely specifies what happens to writes which occur prior to
fork being called and after fork returns.
prev parent reply other threads:[~2013-07-18 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 18:19 preempted dup_mm misses TLB invalidate Nickolas Fortino
2013-07-17 19:27 ` Catalin Marinas
2013-07-17 19:52 ` Stephen Warren
2013-07-17 20:01 ` Russell King - ARM Linux
2013-07-17 20:11 ` Stephen Warren
2013-07-17 20:09 ` Nickolas Fortino
2013-07-17 20:34 ` Russell King - ARM Linux
2013-07-17 21:03 ` Nickolas Fortino
2013-07-17 21:21 ` Russell King - ARM Linux
2013-07-18 1:48 ` Nickolas Fortino [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=51E74975.9040105@nvidia.com \
--to=nfortino@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.