public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: rkir@google.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space: add a driver
Date: Tue, 22 Jan 2019 12:07:12 +0100	[thread overview]
Message-ID: <20190122110712.GA1004@kroah.com> (raw)
In-Reply-To: <20190109021112.5836-2-rkir@google.com>

On Tue, Jan 08, 2019 at 06:11:11PM -0800, rkir@google.com wrote:
> From: Roman Kiryanov <rkir@google.com>
> 
> 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.
> 
> Signed-off-by: Roman Kiryanov <rkir@google.com>
> ---
> Changes in v3:
>  - No changes.
> 
> Changes in v2:
>  - Removed WARN_ON.
>  - Moved to drivers/platform/goldfish (from drivers/misc).
> 
>  drivers/platform/goldfish/Kconfig             |   9 +
>  drivers/platform/goldfish/Makefile            |   1 +
>  .../goldfish/goldfish_address_space.c         | 666 ++++++++++++++++++
>  .../linux/goldfish/goldfish_address_space.h   |  27 +
>  4 files changed, 703 insertions(+)
>  create mode 100644 drivers/platform/goldfish/goldfish_address_space.c
>  create mode 100644 include/uapi/linux/goldfish/goldfish_address_space.h
> 
> diff --git a/drivers/platform/goldfish/Kconfig b/drivers/platform/goldfish/Kconfig
> index 74fdfa68d1f2..60ecec4a3c59 100644
> --- a/drivers/platform/goldfish/Kconfig
> +++ b/drivers/platform/goldfish/Kconfig
> @@ -16,4 +16,13 @@ config GOLDFISH_PIPE
>  	  This is a virtual device to drive the QEMU pipe interface used by
>  	  the Goldfish Android Virtual Device.
>  
> +config GOLDFISH_ADDRESS_SPACE
> +	tristate "A Goldfish driver that talks to the memory sharing device in QEMU"
> +	depends on PCI
> +	depends on GOLDFISH
> +	help
> +	  A Goldfish driver that allocates address space ranges in the guest to
> +	  populate them later in the host. This allows sharing host's memory
> +	  with the guest.

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?

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

thanks,

greg k-h

  parent reply	other threads:[~2019-01-22 11:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09  2:11 [PATCH v3 1/3] drivers: platform: goldfish: fix the checkpatch complain in Kconfig rkir
2019-01-09  2:11 ` [PATCH v3 2/3] drivers: platform: goldfish: goldfish_address_space: add a driver rkir
2019-01-09  8:31   ` Greg KH
2019-01-10  1:41     ` Roman Kiryanov
2019-01-16  4:53       ` Roman Kiryanov
2019-01-22 11:07   ` Greg KH [this message]
2019-01-29  8:32     ` Roman Kiryanov
2019-01-29  9:37       ` Greg KH
2019-01-30 14:44       ` Greg KH
2019-01-31  3:56         ` Roman Kiryanov
2019-01-09  2:11 ` [PATCH v3 3/3] drivers: platform: goldfish: goldfish_sync: " rkir
2019-01-22 11:08   ` Greg KH

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=20190122110712.GA1004@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkir@google.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