From: Will Deacon <will.deacon@arm.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: mark.rutland@arm.com, linux-nvdimm@lists.01.org,
catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/6] arm64 pmem support
Date: Mon, 7 Aug 2017 19:34:12 +0100 [thread overview]
Message-ID: <20170807183411.GD29632@arm.com> (raw)
In-Reply-To: <cover.1500397441.git.robin.murphy@arm.com>
On Tue, Jul 25, 2017 at 11:55:37AM +0100, Robin Murphy wrote:
> With the latest updates to the pmem API, the arch code contribution
> becomes very straightforward to wire up - I think there's about as
> much code here to just cope with the existence of our new instruction
> as there is to actually make use of it. I don't have access to any
> NVDIMMs nor suitable hardware to put them in, so this is written purely
> to spec - the extent of testing has been the feature detection on a
> v8.2 Fast Model vs. v8.0 systems.
>
> Patch #1 could go in as a fix ahead of the rest; it just needs to come
> before patch #5 to prevent that blowing up the build.
Modulo my two comments:
Reviewed-by: Will Deacon <will.deacon@arm.com>
Will
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] arm64 pmem support
Date: Mon, 7 Aug 2017 19:34:12 +0100 [thread overview]
Message-ID: <20170807183411.GD29632@arm.com> (raw)
In-Reply-To: <cover.1500397441.git.robin.murphy@arm.com>
On Tue, Jul 25, 2017 at 11:55:37AM +0100, Robin Murphy wrote:
> With the latest updates to the pmem API, the arch code contribution
> becomes very straightforward to wire up - I think there's about as
> much code here to just cope with the existence of our new instruction
> as there is to actually make use of it. I don't have access to any
> NVDIMMs nor suitable hardware to put them in, so this is written purely
> to spec - the extent of testing has been the feature detection on a
> v8.2 Fast Model vs. v8.0 systems.
>
> Patch #1 could go in as a fix ahead of the rest; it just needs to come
> before patch #5 to prevent that blowing up the build.
Modulo my two comments:
Reviewed-by: Will Deacon <will.deacon@arm.com>
Will
next prev parent reply other threads:[~2017-08-07 18:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 10:55 [PATCH 0/6] arm64 pmem support Robin Murphy
2017-07-25 10:55 ` Robin Murphy
2017-07-25 10:55 ` [PATCH 1/6] arm64: mm: Fix set_memory_valid() declaration Robin Murphy
2017-07-25 10:55 ` Robin Murphy
2017-07-25 10:55 ` [PATCH 2/6] arm64: Convert __inval_cache_range() to area-based Robin Murphy
2017-07-25 10:55 ` Robin Murphy
2017-07-25 10:55 ` [PATCH 3/6] arm64: Expose DC CVAP to userspace Robin Murphy
2017-07-25 10:55 ` Robin Murphy
2017-07-25 10:55 ` [PATCH 4/6] arm64: Handle trapped DC CVAP Robin Murphy
2017-07-25 10:55 ` Robin Murphy
2017-07-25 10:55 ` [PATCH 5/6] arm64: Implement pmem API support Robin Murphy
2017-07-25 10:55 ` Robin Murphy
2017-08-04 15:25 ` Catalin Marinas
2017-08-04 15:25 ` Catalin Marinas
2017-08-04 17:43 ` Robin Murphy
2017-08-04 17:43 ` Robin Murphy
2017-08-04 18:09 ` Dan Williams
2017-08-04 18:09 ` Dan Williams
2017-08-04 18:35 ` Robin Murphy
2017-08-04 18:35 ` Robin Murphy
2017-08-04 19:36 ` Dan Williams
2017-08-04 19:36 ` Dan Williams
2017-08-07 18:33 ` Will Deacon
2017-08-07 18:33 ` Will Deacon
2017-07-25 10:55 ` [PATCH 6/6] arm64: uaccess: Implement *_flushcache variants Robin Murphy
2017-07-25 10:55 ` Robin Murphy
2017-08-07 18:32 ` Will Deacon
2017-08-07 18:32 ` Will Deacon
2017-08-10 10:58 ` Arnd Bergmann
2017-08-10 10:58 ` Arnd Bergmann
2017-08-10 14:12 ` Catalin Marinas
2017-08-10 14:12 ` Catalin Marinas
2017-08-07 18:34 ` Will Deacon [this message]
2017-08-07 18:34 ` [PATCH 0/6] arm64 pmem support Will Deacon
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=20170807183411.GD29632@arm.com \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.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 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.