All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	conor@kernel.org, paul.walmsley@sifive.com, palmer@rivosinc.com,
	aou@eecs.berkeley.edu, anup@brainfault.org,
	konstantin@linuxfoundation.org, linux-doc@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
	mick@ics.forth.gr, jrtc27@jrtc27.com, rdunlap@infradead.org,
	alexghiti@rivosinc.com
Subject: Re: [PATCH v10 0/4] RISC-V: mm: Make SV48 the default address space
Date: Wed, 30 Aug 2023 13:20:34 +0000	[thread overview]
Message-ID: <169340163463.19859.14293662814940071934.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230809232218.849726-1-charlie@rivosinc.com>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed,  9 Aug 2023 16:22:00 -0700 you wrote:
> Make sv48 the default address space for mmap as some applications
> currently depend on this assumption. Users can now select a
> desired address space using a non-zero hint address to mmap. Previously,
> requesting the default address space from mmap by passing zero as the hint
> address would result in using the largest address space possible. Some
> applications depend on empty bits in the virtual address space, like Go and
> Java, so this patch provides more flexibility for application developers.
> 
> [...]

Here is the summary with links:
  - [v10,1/4] RISC-V: mm: Restrict address space for sv39,sv48,sv57
    https://git.kernel.org/riscv/c/add2cc6b6515
  - [v10,2/4] RISC-V: mm: Add tests for RISC-V mm
    https://git.kernel.org/riscv/c/4d0c04eac0c2
  - [v10,3/4] RISC-V: mm: Update pgtable comment documentation
    https://git.kernel.org/riscv/c/26eee2bfc477
  - [v10,4/4] RISC-V: mm: Document mmap changes
    https://git.kernel.org/riscv/c/7998abe69d3c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	conor@kernel.org, paul.walmsley@sifive.com, palmer@rivosinc.com,
	aou@eecs.berkeley.edu, anup@brainfault.org,
	konstantin@linuxfoundation.org, linux-doc@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
	mick@ics.forth.gr, jrtc27@jrtc27.com, rdunlap@infradead.org,
	alexghiti@rivosinc.com
Subject: Re: [PATCH v10 0/4] RISC-V: mm: Make SV48 the default address space
Date: Wed, 30 Aug 2023 13:20:34 +0000	[thread overview]
Message-ID: <169340163463.19859.14293662814940071934.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230809232218.849726-1-charlie@rivosinc.com>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed,  9 Aug 2023 16:22:00 -0700 you wrote:
> Make sv48 the default address space for mmap as some applications
> currently depend on this assumption. Users can now select a
> desired address space using a non-zero hint address to mmap. Previously,
> requesting the default address space from mmap by passing zero as the hint
> address would result in using the largest address space possible. Some
> applications depend on empty bits in the virtual address space, like Go and
> Java, so this patch provides more flexibility for application developers.
> 
> [...]

Here is the summary with links:
  - [v10,1/4] RISC-V: mm: Restrict address space for sv39,sv48,sv57
    https://git.kernel.org/riscv/c/add2cc6b6515
  - [v10,2/4] RISC-V: mm: Add tests for RISC-V mm
    https://git.kernel.org/riscv/c/4d0c04eac0c2
  - [v10,3/4] RISC-V: mm: Update pgtable comment documentation
    https://git.kernel.org/riscv/c/26eee2bfc477
  - [v10,4/4] RISC-V: mm: Document mmap changes
    https://git.kernel.org/riscv/c/7998abe69d3c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2023-08-30 18:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 23:22 [PATCH v10 0/4] RISC-V: mm: Make SV48 the default address space Charlie Jenkins
2023-08-09 23:22 ` Charlie Jenkins
2023-08-09 23:22 ` [PATCH v10 1/4] RISC-V: mm: Restrict address space for sv39,sv48,sv57 Charlie Jenkins
2023-08-09 23:22   ` Charlie Jenkins
2023-08-09 23:22 ` [PATCH v10 2/4] RISC-V: mm: Add tests for RISC-V mm Charlie Jenkins
2023-08-09 23:22   ` Charlie Jenkins
2023-08-09 23:22 ` [PATCH v10 3/4] RISC-V: mm: Update pgtable comment documentation Charlie Jenkins
2023-08-09 23:22   ` Charlie Jenkins
2023-08-09 23:22 ` [PATCH v10 4/4] RISC-V: mm: Document mmap changes Charlie Jenkins
2023-08-09 23:22   ` Charlie Jenkins
2023-08-30 13:20 ` patchwork-bot+linux-riscv [this message]
2023-08-30 13:20   ` [PATCH v10 0/4] RISC-V: mm: Make SV48 the default address space patchwork-bot+linux-riscv
2024-01-13 17:26 ` Yangyu Chen
2024-01-13 17:26   ` Yangyu Chen
2024-01-20  1:34   ` Charlie Jenkins
2024-01-20  1:34     ` Charlie Jenkins
2024-01-20  6:13     ` Yangyu Chen
2024-01-20  6:13       ` Yangyu Chen
2024-01-20  6:49       ` Charlie Jenkins
2024-01-20  6:49         ` Charlie Jenkins
2024-01-20  7:09         ` Yangyu Chen
2024-01-20  7:09           ` Yangyu Chen
2024-01-22 19:56           ` Charlie Jenkins
2024-01-22 19:56             ` Charlie Jenkins

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=169340163463.19859.14293662814940071934.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alexghiti@rivosinc.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=conor@kernel.org \
    --cc=jrtc27@jrtc27.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mick@ics.forth.gr \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rdunlap@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.