[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC v4 PATCH 00/49] Initial support of multi-process qemu - status
From: |
Stefan Hajnoczi |
Subject: |
Re: [RFC v4 PATCH 00/49] Initial support of multi-process qemu - status update |
Date: |
Thu, 2 Jan 2020 10:00:59 +0000 |
On Fri, Dec 20, 2019 at 09:15:40AM -0800, John G Johnson wrote:
> > On Dec 19, 2019, at 5:36 AM, Stefan Hajnoczi <address@hidden> wrote:
> > On Wed, Dec 18, 2019 at 01:00:55AM +0100, Paolo Bonzini wrote:
> >> On 17/12/19 23:57, Felipe Franciosi wrote:
> We don’t pin guest memory; we pass the QEMU file descriptors used to create
> guest memory to the emulation program, and it mmap()s them itself. (ala
> vhost-user).
Does muser really require pinning? If yes, then it seems like a
limitation that can be removed in the future.
Stefan
signature.asc
Description: PGP signature
- Re: [RFC v4 PATCH 00/49] Initial support of multi-process qemu - status update,
Stefan Hajnoczi <=
Re: [RFC v4 PATCH 00/49] Initial support of multi-process qemu - status update, Elena Ufimtseva, 2020/01/02