qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Damien Millescamps <damien.millescamps@6wind.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RESEND] ivshmem: allow the sharing of hugepages
Date: Mon, 16 Sep 2013 15:41:41 +0200	[thread overview]
Message-ID: <52370A95.3000103@6wind.com> (raw)
In-Reply-To: <20130916130753.GM6005@redhat.com>

On 09/16/2013 03:07 PM, Daniel P. Berrange wrote:
> IME this kind of auto-magical fallback behaviour is a bad idea. If we
> want to support non-SHM files for the ivshmem device, then it should
> be done with an explicit command line property. eg where we currently
> have a 'size' and 'shm' property on the cli:
>
>    -device ivshmem,size=24124324,shm=nameofshmobj
>
> it could allow an alternative 'file' property to point to a pre-created
> filename
>
>    -device ivshmem,file=/some/file/path
This patch was based on the fact that in the glibc, shm_open() is
nothing more than an open() with /dev/shm/ prepended to the shared
memory object name. Hence, only a small modification was needed to
change this behavior.

Indeed, having different parameters to specify between a file and a
POSIX shared memory object should be clearer for the user experience.

I have reworked the patch and will send it asap.

Thanks,
-- 
Damien

      reply	other threads:[~2013-09-16 13:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16 12:56 [Qemu-devel] [PATCH RESEND] ivshmem: allow the sharing of hugepages Damien Millescamps
2013-09-16 13:07 ` Daniel P. Berrange
2013-09-16 13:41   ` Damien Millescamps [this message]

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=52370A95.3000103@6wind.com \
    --to=damien.millescamps@6wind.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).