From: Richard Henderson <richard.henderson@linaro.org>
To: Beata Michalska <beata.michalska@linaro.org>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, quintela@redhat.com,
dgilbert@redhat.com, shameerali.kolothum.thodi@huawei.com,
eric.auger@redhat.com, qemu-arm@nongnu.org, pbonzini@redhat.com,
alex.bennee@linaro.org
Subject: Re: [PATCH v2 2/4] Memory: Enable writeback for given memory region
Date: Wed, 6 Nov 2019 13:19:59 +0100 [thread overview]
Message-ID: <5c75bd31-213f-88a4-2eee-0046f99f65fe@linaro.org> (raw)
In-Reply-To: <20191105234100.22052-3-beata.michalska@linaro.org>
On 11/6/19 12:40 AM, Beata Michalska wrote:
> +void qemu_ram_writeback(RAMBlock *block, ram_addr_t start, ram_addr_t length)
> +{
> + void *addr = ramblock_ptr(block, start);
> +
> + /*
> + * The requested range might spread up to the very end of the block
> + */
> + if ((start + length) > block->used_length) {
> + qemu_log("%s: sync range outside the block boundaries: "
> + "start: " RAM_ADDR_FMT " length: " RAM_ADDR_FMT
> + " block length: " RAM_ADDR_FMT " Narrowing down ..." ,
> + __func__, start, length, block->used_length);
> + length = block->used_length - start;
> + }
qemu_log_mask w/ GUEST_ERROR? How do we expect the length to overflow?
> +#ifdef CONFIG_LIBPMEM
> + /* The lack of support for pmem should not block the sync */
> + if (ramblock_is_pmem(block)) {
> + pmem_persist(addr, length);
> + } else
> +#endif
Perhaps better to return out of that if block than have the dangling else.
> +/**
> + * Sync changes made to the memory mapped file back to the backing
> + * storage. For POSIX compliant systems this will simply fallback
> + * to regular msync call (thus the required alignment). Otherwise
> + * it will trigger whole file sync (including the metadata case
> + * there is no support to skip that otherwise)
> + *
> + * @addr - start of the memory area to be synced
> + * @length - length of the are to be synced
> + * @align - alignment (expected to be PAGE_SIZE)
> + * @fd - file descriptor for the file to be synced
> + * (mandatory only for POSIX non-compliant systems)
> + */
> +int qemu_msync(void *addr, size_t length, size_t align, int fd)
> +{
> +#ifdef CONFIG_POSIX
> + size_t align_mask;
> +
> + /* Bare minimum of sanity checks on the alignment */
> + /* The start address needs to be a multiple of PAGE_SIZE */
> + align = MAX(align, qemu_real_host_page_size);
> + align_mask = ~(qemu_real_host_page_size - 1);
> + align = (align + ~align_mask) & align_mask;
> +
> + align_mask = ~(align - 1);
I don't understand what you're trying to do with align.
You pass in qemu_host_page_size from the one caller, and then adjust it for
qemu_real_host_page_size?
Why pass in anything at all, and just use qemu_real_host_page_mask?
> + /**
> + * There are no strict reqs as per the length of mapping
> + * to be synced. Still the length needs to follow the address
> + * alignment changes. Additionally - round the size to the multiple
> + * of requested alignment (expected as PAGE_SIZE)
> + */
> + length += ((uintptr_t)addr & (align - 1));
> + length = (length + ~align_mask) & align_mask;
> +
> + addr = (void *)((uintptr_t)addr & align_mask);
> +
> + return msync(addr, length, MS_SYNC);
> +#else /* CONFIG_POSIX */
> + /**
> + * Perform the sync based on the file descriptor
> + * The sync range will most probably be wider than the one
> + * requested - but it will still get the job done
> + */
> + return qemu_fdatasync(fd);
> +#endif /* CONFIG_POSIX */
> +}
r~
next prev parent reply other threads:[~2019-11-06 12:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 23:40 [PATCH v2 0/4] target/arm: Support for Data Cache Clean up to PoP Beata Michalska
2019-11-05 23:40 ` [PATCH v2 1/4] tcg: cputlb: Add probe_read Beata Michalska
2019-11-05 23:40 ` [PATCH v2 2/4] Memory: Enable writeback for given memory region Beata Michalska
2019-11-06 12:19 ` Richard Henderson [this message]
2019-11-07 14:41 ` Beata Michalska
2019-11-07 16:57 ` Alex Bennée
2019-11-07 16:59 ` Peter Maydell
2019-11-05 23:40 ` [PATCH v2 3/4] migration: ram: Switch to ram block writeback Beata Michalska
2019-11-06 14:18 ` Alex Bennée
2019-11-05 23:41 ` [PATCH v2 4/4] target/arm: Add support for DC CVAP & DC CVADP ins Beata Michalska
2019-11-06 12:37 ` Richard Henderson
2023-11-28 11:24 ` Philippe Mathieu-Daudé
2023-11-28 11:34 ` Peter Maydell
2023-11-28 11:44 ` Philippe Mathieu-Daudé
2023-11-28 18:07 ` Richard Henderson
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=5c75bd31-213f-88a4-2eee-0046f99f65fe@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=beata.michalska@linaro.org \
--cc=dgilbert@redhat.com \
--cc=eric.auger@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=shameerali.kolothum.thodi@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).