From: Auger Eric <eric.auger@redhat.com>
To: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: peter.maydell@linaro.org, drjones@redhat.com,
jonathan.cameron@huawei.com, linuxarm@huawei.com,
alex.williamson@redhat.com, zhaoshenglong@huawei.com,
imammedo@redhat.com
Subject: Re: [Qemu-arm] [RFC v2 0/6] hw/arm: Add support for non-contiguous iova regions
Date: Mon, 28 May 2018 16:22:03 +0200 [thread overview]
Message-ID: <f365f305-175c-db54-677d-6f66719b24cd@redhat.com> (raw)
In-Reply-To: <20180516152026.2920-1-shameerali.kolothum.thodi@huawei.com>
Hi Shameer,
On 05/16/2018 05:20 PM, Shameer Kolothum wrote:
> When the kernel reports valid iova ranges as non-contiguous,
> memory should be allocated to Guest in such a way that
> reserved regions(holes) are not visible by Guest.
>
> This series retrieves the valid iova ranges based on the new
> proposed VFIO interface for kernel [1]. It then populates the
> first 1GB ram as a non-pluggable dimm and rest as a pc-dimm if
> the valid iova ranges are non-contiguous.
Some general comments:
- what are your plans with respect to VFIO device hot-plug handling?
IIUC, at the moment, any collision between reserved regions induces by
hot-plugged devices are not detected/handled. I understand mem hotplug
is not supported on aarch64. Would you simply reject the vfio device
hotplug.
- IIUC any reserved window colliding with [4000000, 1GB] cold-plug RAM
segment is show-stopper. How was this 1GB size chosen exactly?
- Currently you create a single PC-DIMM node whereas several ones may be
possible & necessary? Do you plan to support multiple PC-DIMMS node?
- I have started looking at RAM extension on machvirt. I think adding
support of PC-DIMMS through the qemu cmd line is something that we need
to work on, in paralell.
Thanks
Eric
>
> Patch #3 of this series is loosely based on an earlier attempt
> by Kwangwoo Lee to add hotplug/pc-dimm support to arm64[2]
>
> RFC v1[3] --> RFCv2
> -Based on new VFIO kernel interface
> -Part of Mem modelled as pc-dimm
> -Rebased to qemu 2.12.0
>
> [1] https://lkml.org/lkml/2018/4/18/293
> [2] https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg04600.html
> [3] https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg02412.html
>
> Shameer Kolothum (6):
> hw/vfio: Retrieve valid iova ranges from kernel
> hw/arm/virt: Enable dynamic generation of guest RAM memory regions
> hw/arm/virt: Add pc-dimm mem hotplug framework
> hw/arm: Changes required to accommodate non-contiguous DT mem nodes
> hw/arm: ACPI SRAT changes to accommodate non-contiguous mem
> hw/arm: Populate non-contiguous memory regions
>
> default-configs/aarch64-softmmu.mak | 1 +
> hw/arm/boot.c | 91 ++++++---
> hw/arm/virt-acpi-build.c | 24 ++-
> hw/arm/virt.c | 367 +++++++++++++++++++++++++++++++++++-
> hw/vfio/common.c | 108 ++++++++++-
> include/hw/arm/arm.h | 12 ++
> include/hw/arm/virt.h | 3 +
> include/hw/vfio/vfio-common.h | 7 +
> linux-headers/linux/vfio.h | 23 +++
> 9 files changed, 589 insertions(+), 47 deletions(-)
>
next prev parent reply other threads:[~2018-05-28 14:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 15:20 [Qemu-arm] [RFC v2 0/6] hw/arm: Add support for non-contiguous iova regions Shameer Kolothum
2018-05-16 15:20 ` [Qemu-arm] [RFC v2 1/6] hw/vfio: Retrieve valid iova ranges from kernel Shameer Kolothum
2018-05-28 14:21 ` [Qemu-arm] [Qemu-devel] " Auger Eric
2018-05-30 14:43 ` Shameerali Kolothum Thodi
2018-05-16 15:20 ` [Qemu-arm] [RFC v2 2/6] hw/arm/virt: Enable dynamic generation of guest RAM memory regions Shameer Kolothum
2018-05-28 14:21 ` Auger Eric
2018-05-30 14:43 ` Shameerali Kolothum Thodi
2018-05-28 16:47 ` [Qemu-arm] [Qemu-devel] " Andrew Jones
2018-05-30 14:50 ` Shameerali Kolothum Thodi
2018-05-16 15:20 ` [Qemu-devel] [RFC v2 3/6] hw/arm/virt: Add pc-dimm mem hotplug framework Shameer Kolothum
2018-05-28 14:21 ` Auger Eric
2018-05-30 14:46 ` [Qemu-arm] " Shameerali Kolothum Thodi
2018-05-16 15:20 ` [Qemu-arm] [RFC v2 4/6] hw/arm: Changes required to accommodate non-contiguous DT mem nodes Shameer Kolothum
2018-05-28 14:21 ` [Qemu-arm] [Qemu-devel] " Auger Eric
2018-05-30 14:46 ` Shameerali Kolothum Thodi
2018-05-16 15:20 ` [Qemu-arm] [RFC v2 5/6] hw/arm: ACPI SRAT changes to accommodate non-contiguous mem Shameer Kolothum
2018-05-28 14:21 ` Auger Eric
2018-05-28 17:02 ` [Qemu-arm] [Qemu-devel] " Andrew Jones
2018-05-30 14:51 ` Shameerali Kolothum Thodi
2018-05-31 20:15 ` Auger Eric
2018-06-01 11:09 ` Shameerali Kolothum Thodi
2018-05-16 15:20 ` [Qemu-arm] [RFC v2 6/6] hw/arm: Populate non-contiguous memory regions Shameer Kolothum
2018-05-28 14:21 ` [Qemu-devel] " Auger Eric
2018-05-30 14:48 ` [Qemu-arm] " Shameerali Kolothum Thodi
2018-06-05 7:49 ` Shameerali Kolothum Thodi
2018-06-15 15:44 ` [Qemu-arm] [Qemu-devel] " Andrew Jones
2018-06-15 15:54 ` Peter Maydell
2018-06-15 16:13 ` Auger Eric
2018-06-15 16:33 ` Peter Maydell
2018-06-18 9:46 ` [Qemu-arm] " Shameerali Kolothum Thodi
2018-06-15 15:55 ` Auger Eric
2018-05-28 14:22 ` Auger Eric [this message]
2018-05-30 14:39 ` [Qemu-arm] [RFC v2 0/6] hw/arm: Add support for non-contiguous iova regions Shameerali Kolothum Thodi
2018-05-30 15:24 ` Auger Eric
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=f365f305-175c-db54-677d-6f66719b24cd@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=drjones@redhat.com \
--cc=imammedo@redhat.com \
--cc=jonathan.cameron@huawei.com \
--cc=linuxarm@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=zhaoshenglong@huawei.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).