qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: geoff@hostfission.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ivshmem Windows Driver
Date: Mon, 16 Oct 2017 10:20:38 -0500	[thread overview]
Message-ID: <4d957ed9-0430-927c-ec78-672c39f11682@redhat.com> (raw)
In-Reply-To: <5548e41a5668ec0cba9543139327e035@hostfission.com>

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

On 10/15/2017 04:32 AM, geoff--- via Qemu-devel wrote:
> Hi All,
> 
> I am writing some code that needs to share a block of ram between a
> Windows guest and Linux host. For this I am using the ivshmem device and
> I have written a very primitive driver for windows that allows a single
> application to request to memory map the pci bar (shared memory) into
> the program's context using DeviceIoControl.

Note that upstream support of ivshmem is rather lackluster.  Very often,
the first question in response to someone saying "I need ivshmem", is
"Why? and can we accomplish the same task using a better device
instead?"  Without knowing the full use case, it's hard to argue that
ivshmem is the right device to fit the use case.

There have been efforts to propose a better specified and better
structured replacement for ivshmem, such as vhost-pci, but I'm not sure
what status those patches are in, or if it would be a better fit for
your needs.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

  parent reply	other threads:[~2017-10-16 15:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-15  9:32 [Qemu-devel] ivshmem Windows Driver geoff
2017-10-15 11:14 ` Yan Vugenfirer
2017-10-15 12:21   ` geoff
2017-10-15 12:24     ` Yan Vugenfirer
2017-10-15 12:29       ` geoff
2017-10-16 18:31         ` geoff
2017-10-18  5:31           ` Ladi Prosek
2017-10-18  5:50             ` geoff
2017-10-18  6:50               ` Ladi Prosek
2017-10-18  6:56                 ` geoff
2017-10-18 12:34                   ` Ladi Prosek
2017-10-18 15:04                     ` geoff
2017-10-19  8:35                       ` Ladi Prosek
2017-10-19  8:44                         ` geoff
2017-10-19  9:01                           ` Ladi Prosek
2017-10-19  9:07                             ` geoff
2017-10-19  9:41                               ` geoff
2017-10-19  9:51                                 ` Ladi Prosek
2017-10-19 10:42                                   ` geoff
2017-10-16 15:20 ` Eric Blake [this message]
2017-10-16 16:05   ` geoff

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=4d957ed9-0430-927c-ec78-672c39f11682@redhat.com \
    --to=eblake@redhat.com \
    --cc=geoff@hostfission.com \
    --cc=qemu-devel@nongnu.org \
    /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).