From: Eric Blake <eblake@redhat.com>
To: elena.ufimtseva@oracle.com, qemu-devel@nongnu.org
Cc: john.g.johnson@oracle.com, jag.raman@oracle.com,
konrad.wilk@oracle.com, ross.lagerwall@citrix.com,
liran.alon@oracle.com, stefanha@redhat.com, pbonzini@redhat.com,
kanth.ghatraju@oracle.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [RFC PATCH v2 01/35] multi-process: memory: alloc RAM from file at offset
Date: Mon, 17 Jun 2019 14:14:49 -0500 [thread overview]
Message-ID: <ae695f50-fa36-e6b8-9c8f-6e344da40fae@redhat.com> (raw)
In-Reply-To: <20190617181459.29139-1-elena.ufimtseva@oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 916 bytes --]
On 6/17/19 1:14 PM, elena.ufimtseva@oracle.com wrote:
> From: Jagannathan Raman <jag.raman@oracle.com>
>
> Allow RAM MemoryRegion to be created from an offset in a file, instead
> of allocating at offset of 0 by default. This is needed to synchronize
> RAM between QEMU & remote process.
> This will be needed for the following patches.
This message and the rest of the series was sent unthreaded (no
References: or In-Reply-To: headers), which makes it very difficult to
track. You'll want to fix your sending environment to ensure that
threading is preserved correctly.
>
> Signed-off-by: Jagannathan Raman <jag.raman@oracle.com>
> Signed-off-by: John G Johnson <john.g.johnson@oracle.com>
> Signed-off-by: Elena Ufimtseva <elena.ufimtseva@oracle.com>
> ---
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-17 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 18:14 [Qemu-devel] [RFC PATCH v2 01/35] multi-process: memory: alloc RAM from file at offset elena.ufimtseva
2019-06-17 19:14 ` Eric Blake [this message]
2019-06-17 19:46 ` Elena Ufimtseva
2019-06-18 5:12 ` Gerd Hoffmann
2019-09-03 21:16 ` Jag Raman
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=ae695f50-fa36-e6b8-9c8f-6e344da40fae@redhat.com \
--to=eblake@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=john.g.johnson@oracle.com \
--cc=kanth.ghatraju@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=liran.alon@oracle.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ross.lagerwall@citrix.com \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.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).