[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: Brijesh Singh
Subject: Re: [Qemu-devel] [PATCH v7 02/26] exec: add ram_debug_ops support
Date: Wed, 7 Feb 2018 10:33:57 -0600
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0

On 2/7/18 10:19 AM, Eric Blake wrote:
> 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.
> [meta-comment]
> 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.

I am just looking at the my git send email script log and it seems that
after sending the cover-letter patch, exchange server timeout and my
script restarting send from patch 02/.. hence threading got messed up.
sorry about that. If its an issue then I can resend the whole series.


reply via email to

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