From: Thorsten Kohfeldt <thorsten.kohfeldt@gmx.de>
To: Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, qemu-stable@nongnu.org
Cc: pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/2] memory: Convert skip_dump to ram_device and avoid memcpy
Date: Fri, 28 Oct 2016 03:24:59 +0200 [thread overview]
Message-ID: <4fd1c92f-e55b-e05f-da71-cd09cf9873c5@gmx.de> (raw)
In-Reply-To: <20161025181325.11806.98009.stgit@gimli.home>
I tested these
https://lists.nongnu.org/archive/html/qemu-devel/2016-10/msg05900.html
https://lists.nongnu.org/archive/html/qemu-devel/2016-10/msg05901.html
https://lists.nongnu.org/archive/html/qemu-devel/2016-10/msg05902.html
together with [Qemu-devel] [PULL 18/19] vfio/pci: Fix vfio_rtl8168_quirk_data_read add
https://lists.nongnu.org/archive/html/qemu-devel/2016-10/msg03911.html
on top of qemu-stable-2.7.0
successfully on IPFire (Linux) and Windows 10 x64 with the Realtek driver.
I suggest all 3 commits (msg05901, msg05902, and msg03911) should become
serious candidates for qemu-2.7.1.
Regards,
Thorsten
Am 25.10.2016 um 20:17 schrieb Alex Williamson:
> v2: retain ram_device flag to avoid extra cache miss, per Paolo.
>
> Paolo, posting for completeness, I can merge through my tree if you
> want to Ack. Thanks,
>
> Alex
>
> ---
>
> Alex Williamson (2):
> memory: Replace skip_dump flag with "ram_device"
> memory: Don't use memcpy for ram_device regions
>
>
> hw/vfio/common.c | 9 ++----
> hw/vfio/spapr.c | 2 +
> include/exec/memory.h | 47 ++++++++++++++++++++---------
> memory.c | 80 +++++++++++++++++++++++++++++++++++++++++++++++--
> memory_mapping.c | 2 +
> trace-events | 2 +
> 6 files changed, 116 insertions(+), 26 deletions(-)
>
prev parent reply other threads:[~2016-10-28 1:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 18:17 [Qemu-devel] [PATCH v2 0/2] memory: Convert skip_dump to ram_device and avoid memcpy Alex Williamson
2016-10-25 18:17 ` [Qemu-devel] [PATCH v2 1/2] memory: Replace skip_dump flag with "ram_device" Alex Williamson
2016-10-25 18:17 ` [Qemu-devel] [PATCH v2 2/2] memory: Don't use memcpy for ram_device regions Alex Williamson
2016-10-25 20:04 ` [Qemu-devel] [PATCH v2 0/2] memory: Convert skip_dump to ram_device and avoid memcpy Paolo Bonzini
2016-10-28 1:24 ` Thorsten Kohfeldt [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=4fd1c92f-e55b-e05f-da71-cd09cf9873c5@gmx.de \
--to=thorsten.kohfeldt@gmx.de \
--cc=alex.williamson@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).