All of lore.kernel.org
 help / color / mirror / Atom feed
From: rashmica <rashmica.g@gmail.com>
To: Balbir Singh <bsingharora@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: mpe@ellerman.id.au, rashmica.g@gmail.com, benh@kernel.crashing.org
Subject: Re: [PATCH 1/2] powerpc/mm: Flush cache on memory hot(un)plug
Date: Wed, 11 Apr 2018 14:00:03 +1000	[thread overview]
Message-ID: <2ce3da2a-e714-8dc7-bb54-faadbfcb06f9@gmail.com> (raw)
In-Reply-To: <20180406052424.29841-1-bsingharora@gmail.com>



On 06/04/18 15:24, Balbir Singh wrote:
> This patch adds support for flushing potentially dirty
> cache lines when memory is hot-plugged/hot-un-plugged.
> The support is currently limited to 64 bit systems.
>
> The bug was exposed when mappings for a device were
> actually hot-unplugged and plugged in back later.
> A similar issue was observed during the development
> of memtrace, but memtrace does it's own flushing of
> region via a custom routine.
>
> These patches do a flush both on hotplug/unplug to
> clear any stale data in the cache w.r.t mappings,
> there is a small race window where a clean cache
> line may be created again just prior to tearing
> down the mapping.
>
> The patches were tested by disabling the flush
> routines in memtrace and doing I/O on the trace
> file. The system immediately checkstops (quite
> reliablly if prior to the hot-unplug of the memtrace
> region, we memset the regions we are about to
> hot unplug). After these patches no custom flushing
> is needed in the memtrace code.
>
> Signed-off-by: Balbir Singh <bsingharora@gmail.com>

Reviewed-by: Rashmica Gupta <rashmica.g@gmail.com>

  parent reply	other threads:[~2018-04-11  4:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06  5:24 [PATCH 1/2] powerpc/mm: Flush cache on memory hot(un)plug Balbir Singh
2018-04-06  5:24 ` [PATCH 2/2] powerpc/mm/memtrace: Let the arch hotunplug code flush cache Balbir Singh
2018-04-11  4:01   ` rashmica
2018-04-11 11:05   ` Michael Ellerman
2018-04-11 11:25     ` Balbir Singh
2018-04-09 21:14 ` [PATCH 1/2] powerpc/mm: Flush cache on memory hot(un)plug Reza Arbab
2018-04-11  4:00 ` rashmica [this message]
2018-04-24  3:48 ` [1/2] " Michael Ellerman

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=2ce3da2a-e714-8dc7-bb54-faadbfcb06f9@gmail.com \
    --to=rashmica.g@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=bsingharora@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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.