From: Palmer Dabbelt <palmer@rivosinc.com>
To: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-s390@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Palmer Dabbelt <palmer@rivosinc.com>
Subject: [PATCH 1/5] mm: Add a leading 0 to the VM_FAULT_* types
Date: Fri, 2 Dec 2022 19:03:52 -0800 [thread overview]
Message-ID: <20221203030356.3917-2-palmer@rivosinc.com> (raw)
In-Reply-To: <20221203030356.3917-1-palmer@rivosinc.com>
The next patch will add enough codes to need another character, this
adds the 0 to all the existing codes to keep alignment.
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
---
include/linux/mm_types.h | 32 ++++++++++++++++----------------
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 500e536796ca..758eb70829cb 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -862,24 +862,24 @@ typedef __bitwise unsigned int vm_fault_t;
* in DAX)
* @VM_FAULT_COMPLETED: ->fault completed, meanwhile mmap lock released
* @VM_FAULT_HINDEX_MASK: mask HINDEX value
- *
+ * @VM_FAULT_ARCH_*: Architecture-specific VM fault codes.
*/
enum vm_fault_reason {
- VM_FAULT_OOM = (__force vm_fault_t)0x000001,
- VM_FAULT_SIGBUS = (__force vm_fault_t)0x000002,
- VM_FAULT_MAJOR = (__force vm_fault_t)0x000004,
- VM_FAULT_WRITE = (__force vm_fault_t)0x000008,
- VM_FAULT_HWPOISON = (__force vm_fault_t)0x000010,
- VM_FAULT_HWPOISON_LARGE = (__force vm_fault_t)0x000020,
- VM_FAULT_SIGSEGV = (__force vm_fault_t)0x000040,
- VM_FAULT_NOPAGE = (__force vm_fault_t)0x000100,
- VM_FAULT_LOCKED = (__force vm_fault_t)0x000200,
- VM_FAULT_RETRY = (__force vm_fault_t)0x000400,
- VM_FAULT_FALLBACK = (__force vm_fault_t)0x000800,
- VM_FAULT_DONE_COW = (__force vm_fault_t)0x001000,
- VM_FAULT_NEEDDSYNC = (__force vm_fault_t)0x002000,
- VM_FAULT_COMPLETED = (__force vm_fault_t)0x004000,
- VM_FAULT_HINDEX_MASK = (__force vm_fault_t)0x0f0000,
+ VM_FAULT_OOM = (__force vm_fault_t)0x0000001,
+ VM_FAULT_SIGBUS = (__force vm_fault_t)0x0000002,
+ VM_FAULT_MAJOR = (__force vm_fault_t)0x0000004,
+ VM_FAULT_WRITE = (__force vm_fault_t)0x0000008,
+ VM_FAULT_HWPOISON = (__force vm_fault_t)0x0000010,
+ VM_FAULT_HWPOISON_LARGE = (__force vm_fault_t)0x0000020,
+ VM_FAULT_SIGSEGV = (__force vm_fault_t)0x0000040,
+ VM_FAULT_NOPAGE = (__force vm_fault_t)0x0000100,
+ VM_FAULT_LOCKED = (__force vm_fault_t)0x0000200,
+ VM_FAULT_RETRY = (__force vm_fault_t)0x0000400,
+ VM_FAULT_FALLBACK = (__force vm_fault_t)0x0000800,
+ VM_FAULT_DONE_COW = (__force vm_fault_t)0x0001000,
+ VM_FAULT_NEEDDSYNC = (__force vm_fault_t)0x0002000,
+ VM_FAULT_COMPLETED = (__force vm_fault_t)0x0004000,
+ VM_FAULT_HINDEX_MASK = (__force vm_fault_t)0x00f0000,
};
/* Encode hstate index for a hwpoisoned large page */
--
2.38.1
WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@rivosinc.com>
To: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-s390@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Palmer Dabbelt <palmer@rivosinc.com>
Subject: [PATCH 1/5] mm: Add a leading 0 to the VM_FAULT_* types
Date: Fri, 2 Dec 2022 19:03:52 -0800 [thread overview]
Message-ID: <20221203030356.3917-2-palmer@rivosinc.com> (raw)
In-Reply-To: <20221203030356.3917-1-palmer@rivosinc.com>
The next patch will add enough codes to need another character, this
adds the 0 to all the existing codes to keep alignment.
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
---
include/linux/mm_types.h | 32 ++++++++++++++++----------------
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 500e536796ca..758eb70829cb 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -862,24 +862,24 @@ typedef __bitwise unsigned int vm_fault_t;
* in DAX)
* @VM_FAULT_COMPLETED: ->fault completed, meanwhile mmap lock released
* @VM_FAULT_HINDEX_MASK: mask HINDEX value
- *
+ * @VM_FAULT_ARCH_*: Architecture-specific VM fault codes.
*/
enum vm_fault_reason {
- VM_FAULT_OOM = (__force vm_fault_t)0x000001,
- VM_FAULT_SIGBUS = (__force vm_fault_t)0x000002,
- VM_FAULT_MAJOR = (__force vm_fault_t)0x000004,
- VM_FAULT_WRITE = (__force vm_fault_t)0x000008,
- VM_FAULT_HWPOISON = (__force vm_fault_t)0x000010,
- VM_FAULT_HWPOISON_LARGE = (__force vm_fault_t)0x000020,
- VM_FAULT_SIGSEGV = (__force vm_fault_t)0x000040,
- VM_FAULT_NOPAGE = (__force vm_fault_t)0x000100,
- VM_FAULT_LOCKED = (__force vm_fault_t)0x000200,
- VM_FAULT_RETRY = (__force vm_fault_t)0x000400,
- VM_FAULT_FALLBACK = (__force vm_fault_t)0x000800,
- VM_FAULT_DONE_COW = (__force vm_fault_t)0x001000,
- VM_FAULT_NEEDDSYNC = (__force vm_fault_t)0x002000,
- VM_FAULT_COMPLETED = (__force vm_fault_t)0x004000,
- VM_FAULT_HINDEX_MASK = (__force vm_fault_t)0x0f0000,
+ VM_FAULT_OOM = (__force vm_fault_t)0x0000001,
+ VM_FAULT_SIGBUS = (__force vm_fault_t)0x0000002,
+ VM_FAULT_MAJOR = (__force vm_fault_t)0x0000004,
+ VM_FAULT_WRITE = (__force vm_fault_t)0x0000008,
+ VM_FAULT_HWPOISON = (__force vm_fault_t)0x0000010,
+ VM_FAULT_HWPOISON_LARGE = (__force vm_fault_t)0x0000020,
+ VM_FAULT_SIGSEGV = (__force vm_fault_t)0x0000040,
+ VM_FAULT_NOPAGE = (__force vm_fault_t)0x0000100,
+ VM_FAULT_LOCKED = (__force vm_fault_t)0x0000200,
+ VM_FAULT_RETRY = (__force vm_fault_t)0x0000400,
+ VM_FAULT_FALLBACK = (__force vm_fault_t)0x0000800,
+ VM_FAULT_DONE_COW = (__force vm_fault_t)0x0001000,
+ VM_FAULT_NEEDDSYNC = (__force vm_fault_t)0x0002000,
+ VM_FAULT_COMPLETED = (__force vm_fault_t)0x0004000,
+ VM_FAULT_HINDEX_MASK = (__force vm_fault_t)0x00f0000,
};
/* Encode hstate index for a hwpoisoned large page */
--
2.38.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@rivosinc.com>
To: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-s390@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Palmer Dabbelt <palmer@rivosinc.com>
Subject: [PATCH 1/5] mm: Add a leading 0 to the VM_FAULT_* types
Date: Fri, 2 Dec 2022 19:03:52 -0800 [thread overview]
Message-ID: <20221203030356.3917-2-palmer@rivosinc.com> (raw)
In-Reply-To: <20221203030356.3917-1-palmer@rivosinc.com>
The next patch will add enough codes to need another character, this
adds the 0 to all the existing codes to keep alignment.
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
---
include/linux/mm_types.h | 32 ++++++++++++++++----------------
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 500e536796ca..758eb70829cb 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -862,24 +862,24 @@ typedef __bitwise unsigned int vm_fault_t;
* in DAX)
* @VM_FAULT_COMPLETED: ->fault completed, meanwhile mmap lock released
* @VM_FAULT_HINDEX_MASK: mask HINDEX value
- *
+ * @VM_FAULT_ARCH_*: Architecture-specific VM fault codes.
*/
enum vm_fault_reason {
- VM_FAULT_OOM = (__force vm_fault_t)0x000001,
- VM_FAULT_SIGBUS = (__force vm_fault_t)0x000002,
- VM_FAULT_MAJOR = (__force vm_fault_t)0x000004,
- VM_FAULT_WRITE = (__force vm_fault_t)0x000008,
- VM_FAULT_HWPOISON = (__force vm_fault_t)0x000010,
- VM_FAULT_HWPOISON_LARGE = (__force vm_fault_t)0x000020,
- VM_FAULT_SIGSEGV = (__force vm_fault_t)0x000040,
- VM_FAULT_NOPAGE = (__force vm_fault_t)0x000100,
- VM_FAULT_LOCKED = (__force vm_fault_t)0x000200,
- VM_FAULT_RETRY = (__force vm_fault_t)0x000400,
- VM_FAULT_FALLBACK = (__force vm_fault_t)0x000800,
- VM_FAULT_DONE_COW = (__force vm_fault_t)0x001000,
- VM_FAULT_NEEDDSYNC = (__force vm_fault_t)0x002000,
- VM_FAULT_COMPLETED = (__force vm_fault_t)0x004000,
- VM_FAULT_HINDEX_MASK = (__force vm_fault_t)0x0f0000,
+ VM_FAULT_OOM = (__force vm_fault_t)0x0000001,
+ VM_FAULT_SIGBUS = (__force vm_fault_t)0x0000002,
+ VM_FAULT_MAJOR = (__force vm_fault_t)0x0000004,
+ VM_FAULT_WRITE = (__force vm_fault_t)0x0000008,
+ VM_FAULT_HWPOISON = (__force vm_fault_t)0x0000010,
+ VM_FAULT_HWPOISON_LARGE = (__force vm_fault_t)0x0000020,
+ VM_FAULT_SIGSEGV = (__force vm_fault_t)0x0000040,
+ VM_FAULT_NOPAGE = (__force vm_fault_t)0x0000100,
+ VM_FAULT_LOCKED = (__force vm_fault_t)0x0000200,
+ VM_FAULT_RETRY = (__force vm_fault_t)0x0000400,
+ VM_FAULT_FALLBACK = (__force vm_fault_t)0x0000800,
+ VM_FAULT_DONE_COW = (__force vm_fault_t)0x0001000,
+ VM_FAULT_NEEDDSYNC = (__force vm_fault_t)0x0002000,
+ VM_FAULT_COMPLETED = (__force vm_fault_t)0x0004000,
+ VM_FAULT_HINDEX_MASK = (__force vm_fault_t)0x00f0000,
};
/* Encode hstate index for a hwpoisoned large page */
--
2.38.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-12-03 3:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 3:03 [PATCH 0/5] mm: Stop alaising VM_FAULT_HINDEX_MASK in arch code Palmer Dabbelt
2022-12-03 3:03 ` Palmer Dabbelt
2022-12-03 3:03 ` Palmer Dabbelt
2022-12-03 3:03 ` Palmer Dabbelt [this message]
2022-12-03 3:03 ` [PATCH 1/5] mm: Add a leading 0 to the VM_FAULT_* types Palmer Dabbelt
2022-12-03 3:03 ` Palmer Dabbelt
2022-12-03 3:03 ` [PATCH 2/5] mm: Add VM_FAULT_ARCH_* codes Palmer Dabbelt
2022-12-03 3:03 ` Palmer Dabbelt
2022-12-03 3:03 ` Palmer Dabbelt
2022-12-03 3:03 ` [PATCH 3/5] arm: fault: Convert to " Palmer Dabbelt
2022-12-03 3:03 ` Palmer Dabbelt
2022-12-03 3:03 ` Palmer Dabbelt
2022-12-03 3:03 ` [PATCH 4/5] s390: " Palmer Dabbelt
2022-12-03 3:03 ` Palmer Dabbelt
2022-12-03 3:03 ` Palmer Dabbelt
2022-12-03 3:03 ` [PATCH 5/5] RISC-V: " Palmer Dabbelt
2022-12-03 3:03 ` Palmer Dabbelt
2022-12-03 3:03 ` Palmer Dabbelt
2023-02-03 3:31 ` [PATCH 0/5] mm: Stop alaising VM_FAULT_HINDEX_MASK in arch code Palmer Dabbelt
2023-02-03 3:31 ` Palmer Dabbelt
2023-02-03 3:31 ` Palmer Dabbelt
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=20221203030356.3917-2-palmer@rivosinc.com \
--to=palmer@rivosinc.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.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.