[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH RFC 10/21] ramblock: Add ramblock_file_map()
From: |
Peter Xu |
Subject: |
Re: [PATCH RFC 10/21] ramblock: Add ramblock_file_map() |
Date: |
Wed, 25 Jan 2023 09:46:03 -0500 |
On Wed, Jan 25, 2023 at 09:24:24AM +0000, Dr. David Alan Gilbert wrote:
> > > > static void *file_ram_alloc(RAMBlock *block,
> > > > int fd,
> > > > bool truncate,
> > > > off_t offset,
> > > > Error **errp)
> > > > {
> > > > - uint32_t qemu_map_flags;
> > > > void *area;
> > > >
> > > > /* Remember the offset just in case we'll need to map the range
> > > > again */
> > >
> > > Note that this comment is now wrong; you need to always set that for the
> > > map call.
> >
> > This line is added in patch 7. After this patch, a ramblock should always
> > be mapped with ramblock_file_map(), so it keeps being true?
>
> With ramblock_file_map() it's not a 'just in case' any more though is
> it? This value always goes through the block-> now?
Ah yes.. Since the comment is not extremely informative, instead of
changing it, I can drop it in the previous patch when introduced.
--
Peter Xu
[PATCH RFC 09/21] ramblock: Add RAM_READONLY, Peter Xu, 2023/01/17
[PATCH RFC 11/21] migration: Add hugetlb-doublemap cap, Peter Xu, 2023/01/17
[PATCH RFC 12/21] migration: Introduce page size for-migration-only, Peter Xu, 2023/01/17