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: <20180207160638.98872-1-brijesh.singh@xxxxxxx> > > References: <20180207160638.98872-1-brijesh.singh@xxxxxxx> > > 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: <20180207160324.98614-1-brijesh.singh@xxxxxxx> > > 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. -Brijesh
