From: Jag Raman <jag.raman@oracle.com>
To: Gerd Hoffmann <kraxel@redhat.com>, elena.ufimtseva@oracle.com
Cc: john.g.johnson@oracle.com, konrad.wilk@oracle.com,
qemu-devel@nongnu.org, 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: Tue, 3 Sep 2019 17:16:28 -0400 [thread overview]
Message-ID: <fbb4a8fa-9d6c-c21d-7224-8e8af1fb1601@oracle.com> (raw)
In-Reply-To: <20190618051227.fic3k5ihwwj4zji7@sirius.home.kraxel.org>
On 6/18/2019 1:12 AM, Gerd Hoffmann wrote:
> On Mon, Jun 17, 2019 at 11:14:59AM -0700, 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.
>
> Details please. vhost-user works fine without this ...
Hi Gerd,
Sorry for the delayed response.
vhost-user doesn't use qemu_ram_alloc_from_fd(), it directly calls
mmap() to map the RAM onto the remote process.
Secondly, vhost-user uses its own functions (like vu_gpa_to_va()) for
address translation, whereas multi-process uses QEMU's existing
functions (address_space_rw()). Therefore, multi-process needs to use
qemu_ram_alloc_from_fd().
Lastly, updates to the system memory (received via MemoryListener) are
often in segments and not contiguous. Therefore, mapping these segments
in the remote process is possible only if we are able to allocate a
MemoryRegion at an offset in the memory backend.
Thanks!
--
Jag
>
> cheers,
> Gerd
>
>
prev parent reply other threads:[~2019-09-04 0:50 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
2019-06-17 19:46 ` Elena Ufimtseva
2019-06-18 5:12 ` Gerd Hoffmann
2019-09-03 21:16 ` Jag Raman [this message]
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=fbb4a8fa-9d6c-c21d-7224-8e8af1fb1601@oracle.com \
--to=jag.raman@oracle.com \
--cc=elena.ufimtseva@oracle.com \
--cc=john.g.johnson@oracle.com \
--cc=kanth.ghatraju@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=kraxel@redhat.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).