On 01/25/2017 03:20 PM, Khalid Aziz wrote:
On 01/25/2017 03:00 PM, Rob Gardner wrote:
On 01/25/2017 12:57 PM, Khalid Aziz wrote:
@@ -157,6 +158,24 @@ int __get_user_pages_fast(unsigned long start,
int nr_pages, int write,
pgd_t *pgdp;
int nr = 0;
+#ifdef CONFIG_SPARC64
+if
On 01/25/2017 12:57 PM, Khalid Aziz wrote:
ADI is a new feature supported on SPARC M7 and newer processors to allow
hardware to catch rogue accesses to memory. ADI is supported for data
fetches only and not instruction fetches. An app can enable ADI on its
data pages, set version tags on them and
On 01/13/2017 09:08 AM, Dave Hansen wrote:
On 01/13/2017 07:29 AM, Rob Gardner wrote:
so perhaps ADI should simply be disallowed for memory mapped to
files, and this particular complication can be avoided. Thoughts?
What's a "file" from your perspective?
In Linux, shared m
On 01/13/2017 07:48 AM, Khalid Aziz wrote:
On 01/12/2017 06:31 PM, Rob Gardner wrote:
On 01/12/2017 05:22 PM, Khalid Aziz wrote:
On 01/12/2017 10:53 AM, Dave Hansen wrote:
On 01/12/2017 08:50 AM, Khalid Aziz wrote:
2. Any shared page that has ADI protection enabled on it, must
stay ADI
On 01/12/2017 05:22 PM, Khalid Aziz wrote:
On 01/12/2017 10:53 AM, Dave Hansen wrote:
On 01/12/2017 08:50 AM, Khalid Aziz wrote:
2. Any shared page that has ADI protection enabled on it, must stay ADI
protected across all processes sharing it.
Is that true?
What happens if a page with ADI ta
On 01/12/2017 01:13 PM, Eric Dumazet wrote:
On Thu, 2017-01-12 at 11:59 -0800, Shannon Nelson wrote:
Fix up a data alignment issue on sparc by swapping the order
of the cookie byte array field with the length field in
struct tcp_fastopen_cookie
This addresses log complaints like these:
log
On 01/06/2017 10:18 AM, Khalid Aziz wrote:
On 01/06/2017 10:54 AM, Rob Gardner wrote:
On 01/06/2017 09:10 AM, Khalid Aziz wrote:
On 01/06/2017 10:02 AM, David Miller wrote:
From: Dave Hansen
Date: Fri, 6 Jan 2017 08:55:03 -0800
Actually, that reminds me... How does your code interface
On 01/06/2017 09:10 AM, Khalid Aziz wrote:
On 01/06/2017 10:02 AM, David Miller wrote:
From: Dave Hansen
Date: Fri, 6 Jan 2017 08:55:03 -0800
Actually, that reminds me... How does your code interface with
ksm? Or
is there no interaction needed since you're always working on virtual
address
On 01/04/2017 04:01 PM, Dave Hansen wrote:
On 01/04/2017 03:58 PM, Khalid Aziz wrote:
How does this all work with large pages?
It works with large pages the same way as normal sized pages. The TTE
for a large page also will have the mcd bit set in it and tags are set
and referenced the same way
On 01/04/2017 03:49 PM, Dave Hansen wrote:
On 01/04/2017 03:44 PM, Rob Gardner wrote:
On 01/04/2017 03:40 PM, Dave Hansen wrote:
On 01/04/2017 03:35 PM, Rob Gardner wrote:
Tags are not cleared at all when memory is freed, but rather, lazily
(and automatically) cleared when memory is allocated
On 01/04/2017 03:40 PM, Dave Hansen wrote:
On 01/04/2017 03:35 PM, Rob Gardner wrote:
Tags are not cleared at all when memory is freed, but rather, lazily
(and automatically) cleared when memory is allocated.
What does "allocated" mean in this context? Physical or virtual? What
do
On 01/04/2017 03:27 PM, Dave Hansen wrote:
On 01/04/2017 02:46 PM, Khalid Aziz wrote:
This patch extends mprotect to enable ADI (TSTATE.mcde), enable/disable
MCD (Memory Corruption Detection) on selected memory ranges, enable
TTE.mcd in PTEs, return ADI parameters to userspace and save/restore A
MALL
option if there is no
objections.
CCing David Miller and Rob Gardner. They might be able to explain
more if you
have any more questions. Here is the discussion thread if you guys
want to look at history.
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1237642.html
Yes
On 03/07/2016 10:39 AM, Khalid Aziz wrote:
On 03/07/2016 11:12 AM, Dave Hansen wrote:
On 03/07/2016 09:53 AM, Andy Lutomirski wrote:
Also, what am I missing? Tying these tags to the physical page seems
like a poor design to me. This seems really awkward to use.
Yeah, can you describe the st
On 03/07/2016 10:24 AM, Khalid Aziz wrote:
Tags can be cleared by user by setting tag to 0. Tags are
automatically cleared by the hardware when the mapping for a virtual
address is removed from TSB (which is why swappable pages are a
problem), so kernel does not have to do it as part of clean
On 03/07/2016 01:38 PM, David Miller wrote:
From: Khalid Aziz
Date: Mon, 7 Mar 2016 14:33:56 -0700
On 03/07/2016 12:16 PM, David Miller wrote:
From: Khalid Aziz
Date: Mon, 7 Mar 2016 11:24:54 -0700
Tags can be cleared by user by setting tag to 0. Tags are
automatically cleared by the hardw
On 03/07/2016 01:33 PM, Khalid Aziz wrote:
That is a possibility but limited in scope. An address range covered
by a single TTE can have large number of tags. Version tags are set on
cacheline. In extreme case, one could set a tag for each set of
64-bytes in a page. Also tags are set complete
On 03/07/2016 10:04 AM, Khalid Aziz wrote:
On 03/07/2016 09:56 AM, David Miller wrote:
From: Khalid Aziz
Date: Mon, 7 Mar 2016 08:07:53 -0700
PR_GET_SPARC_ADICAPS
Put this into a new ELF auxiliary vector entry via ARCH_DLINFO.
So now all that's left is supposedly the TAG stuff, please expl
On 03/07/2016 07:07 AM, Khalid Aziz wrote:
On 03/05/2016 09:07 PM, David Miller wrote:
From: Khalid Aziz
Date: Wed, 2 Mar 2016 13:39:37 -0700
In this
first implementation I am enabling ADI for hugepages only
since these pages are locked in memory and hence avoid the
issue of
19 matches
Mail list logo
