Re: [PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space: add a driver

2019-01-30 Thread Roman Kiryanov
> Also, why does the other Android "emulator", cuttlefish, not need > special drivers like this and the other goldfish drivers? Shouldn't you > be using the same interfaces that they use that are already merged > upstream? > Actually, now that cuttlefish works on a mainline kernel, can't we just

Re: [PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space: add a driver

2019-01-30 Thread Greg KH
On Tue, Jan 29, 2019 at 12:32:12AM -0800, Roman Kiryanov wrote: > > 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 > >

Re: [PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space: add a driver

2019-01-29 Thread Greg KH
On Tue, Jan 29, 2019 at 12:32:12AM -0800, Roman Kiryanov wrote: > > 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 > >

Re: [PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space: add a driver

2019-01-29 Thread Roman Kiryanov
> 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

Re: [PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space: add a driver

2019-01-22 Thread Greg KH
On Tue, Jan 08, 2019 at 06:11:11PM -0800, r...@google.com wrote: > From: Roman Kiryanov > > A driver for the Goldfish Android emulator that occupies > address space to use it with the memory sharing device > on the QEMU side. The memory sharding device allocates > subranges and populate them

Re: [PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space: add a driver

2019-01-15 Thread Roman Kiryanov
> > Do you have a pointer to the QEMU commit that matches up with the device > > that this driver is supposed to be supporting? > > The device code is here: > > https://android.googlesource.com/platform/external/qemu/+/emu-master-dev/hw/pci/goldfish_address_space.c Hi Greg, do you need anything

Re: [PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space: add a driver

2019-01-09 Thread Roman Kiryanov
> Do you have a pointer to the QEMU commit that matches up with the device > that this driver is supposed to be supporting? The device code is here: https://android.googlesource.com/platform/external/qemu/+/emu-master-dev/hw/pci/goldfish_address_space.c Regards, Roman.

Re: [PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space: add a driver

2019-01-09 Thread Greg KH
On Tue, Jan 08, 2019 at 06:11:11PM -0800, r...@google.com wrote: > From: Roman Kiryanov > > A driver for the Goldfish Android emulator that occupies > address space to use it with the memory sharing device > on the QEMU side. The memory sharding device allocates > subranges and populate them

[PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space: add a driver

2019-01-08 Thread rkir
From: Roman Kiryanov A driver for the Goldfish Android emulator that occupies address space to use it with the memory sharing device on the QEMU side. The memory sharding device allocates subranges and populate them with actual RAM. This allows sharing host's memory with the guest.