From: Eric Blake <eblake@redhat.com>
To: Samuel Pitoiset <samuel.pitoiset@gmail.com>, qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com
Subject: Re: [Qemu-devel] [PATCH] vfio: allow to disable MMAP per device with -x-mmap=off option
Date: Tue, 24 Feb 2015 14:40:13 -0700 [thread overview]
Message-ID: <54ECEFBD.8000200@redhat.com> (raw)
In-Reply-To: <1424810331-25657-1-git-send-email-samuel.pitoiset@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
On 02/24/2015 01:38 PM, Samuel Pitoiset wrote:
> Disabling MMAP support uses the slower read/write accesses but allows to
> trace all MMIO accesses, which is not good for performance, but very
> useful for reverse engineering PCI drivers. This option allows to
> disable MMAP per device without a compile-time change.
>
> Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>
> ---
> hw/vfio/common.c | 2 +-
> hw/vfio/pci.c | 1 +
> include/hw/vfio/vfio-common.h | 2 +-
> 3 files changed, 3 insertions(+), 2 deletions(-)
> +++ b/hw/vfio/pci.c
> @@ -3456,6 +3456,7 @@ static Property vfio_pci_dev_properties[] = {
> DEFINE_PROP_BIT("x-vga", VFIOPCIDevice, features,
> VFIO_FEATURE_ENABLE_VGA_BIT, false),
> DEFINE_PROP_INT32("bootindex", VFIOPCIDevice, bootindex, -1),
> + DEFINE_PROP_BOOL("x-mmap", VFIOPCIDevice, vbasedev.allow_mmap, true),
Naming it 'x-mmap' implies it is experimental and may be removed
someday. Is there any reason why you are not proposing it as a
permanent knob?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-02-24 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 20:38 [Qemu-devel] [PATCH] vfio: allow to disable MMAP per device with -x-mmap=off option Samuel Pitoiset
2015-02-24 21:40 ` Eric Blake [this message]
2015-02-24 21:53 ` Alex Williamson
2015-02-25 3:04 ` Eric Blake
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=54ECEFBD.8000200@redhat.com \
--to=eblake@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.pitoiset@gmail.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;
as well as URLs for NNTP newsgroup(s).