[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH V4 03/19] memory: add RAM_PRIVATE
|
From: |
Peter Xu |
|
Subject: |
Re: [PATCH V4 03/19] memory: add RAM_PRIVATE |
|
Date: |
Mon, 9 Dec 2024 14:45:48 -0500 |
On Mon, Dec 02, 2024 at 05:19:55AM -0800, Steve Sistare wrote:
> Define the RAM_PRIVATE flag.
>
> In RAMBlock creation functions, if MAP_SHARED is 0 in the flags parameter,
> in a subsequent patch the implementation may still create a shared mapping
> if other conditions require it. Callers who specifically want a private
> mapping, eg for objects specified by the user, must pass RAM_PRIVATE.
>
> After RAMBlock creation, MAP_SHARED in the block's flags indicates whether
> the block is shared or private, and MAP_PRIVATE is omitted.
>
> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
- [PATCH V4 13/19] migration: cpr-transfer save and load, (continued)
- [PATCH V4 01/19] backends/hostmem-shm: factor out allocation of "anonymous shared memory with an fd", Steve Sistare, 2024/12/02
- [PATCH V4 03/19] memory: add RAM_PRIVATE, Steve Sistare, 2024/12/02
- Re: [PATCH V4 03/19] memory: add RAM_PRIVATE,
Peter Xu <=
- [PATCH V4 05/19] migration: cpr-state, Steve Sistare, 2024/12/02
- [PATCH V4 02/19] physmem: fd-based shared memory, Steve Sistare, 2024/12/02
- Re: [PATCH V4 02/19] physmem: fd-based shared memory, Peter Xu, 2024/12/09
- Re: [PATCH V4 02/19] physmem: fd-based shared memory, Steven Sistare, 2024/12/12
- Re: [PATCH V4 02/19] physmem: fd-based shared memory, Peter Xu, 2024/12/12
- Re: [PATCH V4 02/19] physmem: fd-based shared memory, Steven Sistare, 2024/12/13
- Re: [PATCH V4 02/19] physmem: fd-based shared memory, Steven Sistare, 2024/12/13
- Re: [PATCH V4 02/19] physmem: fd-based shared memory, Peter Xu, 2024/12/16
- Re: [PATCH V4 02/19] physmem: fd-based shared memory, Steven Sistare, 2024/12/17
- Re: [PATCH V4 02/19] physmem: fd-based shared memory, Peter Xu, 2024/12/17