Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20190109021112.5836-1-rkir@google.com> <20190109021112.5836-2-rkir@google.com>
 <20190122110712.GA1004@kroah.com>
In-Reply-To: <20190122110712.GA1004@kroah.com>
From:   Roman Kiryanov <rkir@google.com>
Date:   Tue, 29 Jan 2019 00:32:12 -0800
Message-ID: <CAOGAQeo1Kv55EUn2sYPOt9EgBMfN=+o_A4KOPVgqbJHo+HN-Sw@mail.gmail.com>
Subject: Re: [PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space:
 add a driver
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

> How does QEMU do this today?  There isn't a virtio or some other virtual
> memory device that allows memory regions to be shared?  I can't believe
> that there isn't one yet.  If not, then this should be some kind of
> "generic" QEMU memory device, not a "goldfish" specific one, right?

I also thought this should not be something unique to us. So I asked
in our internal mailing list, I heard nothing back.

> Please work with the QEMU developers on this, I need their ack before I
> can take something like this.

This is a good point. I asked there (nothing since 1/24):

http://lists.nongnu.org/archive/html/qemu-discuss/2019-01/msg00055.html

When we were working on our device side, we had to change some QEMU
code and later noticed that HAXM also requires some fixes (we had
meetings with Intel). I suppose QEMU does not have this feature yet.

Could you please tell if we can proceed with upstreaming as is?

Regards,
Roman.