[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v7 02/26] exec: add ram_debug_ops support

From: Eric Blake
Subject: Re: [Qemu-devel] [PATCH v7 02/26] exec: add ram_debug_ops support
Date: Wed, 7 Feb 2018 10:19:48 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2

On 02/07/2018 10:06 AM, Brijesh Singh wrote:
Currently, the guest memory access for the debug purpose is performed
using the memcpy(). Lets extend the 'struct MemoryRegion' to include
ram_debug_ops callbacks. The ram_debug_ops can be used to override
memcpy() with something else.


Your threading is off.  This email was sent with the headers:

> In-Reply-To: <address@hidden>
> References: <address@hidden>

which ties it only to patch 1/26; in turn, that message has no In-Reply-To header at all, making it a top-level thread. Meanwhile, your 0/26 cover letter has:

Message-Id: <address@hidden>

which nothing in the rest of the series refers to, making it a separate thread. It would be helpful if you could the threading used in your sending environment, although I don't have any specific suggestions on what that fix would be.

Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]