On Thu, 7 Nov 2019 at 16:57, Alex Bennée wrote:
>
>
> Beata Michalska writes:
>
> > On Wed, 6 Nov 2019 at 12:20, Richard Henderson
> > wrote:
> >> qemu_log_mask w/ GUEST_ERROR? How do we expect the length to overflow?
> >
> > In theory it shouldn't, at least with current usage.
> > I guess the
Beata Michalska writes:
> On Wed, 6 Nov 2019 at 12:20, Richard Henderson
> wrote:
>>
>> 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);
>> > +
>> > +
On Wed, 6 Nov 2019 at 12:20, Richard Henderson
wrote:
>
> 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 m
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 + l
Add an option to trigger memory writeback to sync given memory region
with the corresponding backing store, case one is available.
This extends the support for persistent memory, allowing syncing on-demand.
Signed-off-by: Beata Michalska
---
exec.c | 43 +
