qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Auger Eric <eric.auger@redhat.com>
To: zhuyijun@huawei.com, qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, shameerali.kolothum.thodi@huawei.com,
	zhaoshenglong@huawei.com
Subject: Re: [Qemu-devel] [RFC 0/5] arm: Exclude reserved memory regions of iommu to avoid
Date: Mon, 13 Nov 2017 21:01:34 +0100	[thread overview]
Message-ID: <db7ef4f4-f95e-bb45-0a1a-5c40ca186956@redhat.com> (raw)
In-Reply-To: <1510576145-23084-1-git-send-email-zhuyijun@huawei.com>

Hello Zhu,

On 13/11/2017 13:29, zhuyijun@huawei.com wrote:
> From: Zhu Yijun <zhuyijun@huawei.com>
> 
> With kernel 4.11, iommu/smmu will populate the MSI IOVA reserved window and
> PCI reserved window which has to be excluded from Guest iova allocations.
> 
> And on certain HiSilicon platforms (hip06/hip07), the GIC ITS and PCIe RC 
> deviates from the standard implementation will reserve the hw msi regions in
> the smmu-v3 driver which means these address regions will not be translated.
> 
> https://www.spinics.net/lists/linux-pci/msg65125.html
> 
> On such platforms, reserved memory regions will export like this:
> 
> root:~# cat /sys/kernel/iommu_groups/7/reserved_regions
> 0x00000000a8800000 0x00000000affeffff reserved
> 0x00000000c6000000 0x00000000c601ffff msi
> 
> However, it falls within the Qemu default virtual memory address space.
> 
> Take a look at hw/arm/virt.c:
> 
> [VIRT_MEM] =             { 0x40000000, RAMLIMIT_BYTES },
>     . . .
> 
>     memory_region_allocate_system_memory(ram, NULL, "mach-virt.ram",
>                                                      machine->ram_size);
> memory_region_add_subregion(sysmem, vms->memmap[VIRT_MEM].base, ram);
> 
> So suppose we allocate 4GB mem to a VM, there is a chance that the reserved
> regions will get allocated for a Guest VF DMA iova and it will fail.
> 
> This patchset create holes in the Qemu RAM address space which exclude
> the sysfs exported regions.
> 
> 
> Zhu Yijun (5):
>   hw/vfio: Add function for getting reserved_region of device iommu
>     group
>   hw/arm/virt: Enable dynamic generation of guest RAM memory regions
>   hw/arm: add scattered RAM memory region support
>   hw/arm/boot: set fdt size cell of memory node from mem_list
>   hw/arm/virt-acpi-build: Build srat table according to mem_list
I have not received all the patches of this series. I miss 2, 4, 5.

Looking at
https://lists.nongnu.org/archive/html/qemu-devel/2017-11/threads.html#02198,
I don't see them either.

Thanks

Eric
> 
>  hw/arm/boot.c                 | 155 +++++++++++++++++++++++++++++++-----------
>  hw/arm/virt-acpi-build.c      |  40 +++++++++--
>  hw/arm/virt.c                 | 120 ++++++++++++++++++++++++++++++--
>  hw/vfio/common.c              |  67 ++++++++++++++++++
>  hw/vfio/pci.c                 |   2 +
>  hw/vfio/platform.c            |   2 +
>  include/exec/memory.h         |   7 ++
>  include/hw/arm/arm.h          |   1 +
>  include/hw/arm/virt.h         |   1 +
>  include/hw/vfio/vfio-common.h |   3 +
>  10 files changed, 347 insertions(+), 51 deletions(-)
> 

  parent reply	other threads:[~2017-11-13 20:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 12:29 [Qemu-devel] [RFC 0/5] arm: Exclude reserved memory regions of iommu to avoid zhuyijun
2017-11-13 12:29 ` [Qemu-devel] [RFC 1/5] hw/vfio: Add function for getting reserved_region of device iommu group zhuyijun
2017-11-13 12:29 ` [Qemu-devel] [RFC 3/5] hw/arm: add scattered RAM memory region support zhuyijun
2017-11-13 20:01 ` Auger Eric [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-14  1:15 [Qemu-devel] [RFC 0/5] arm: Exclude reserved memory regions of iommu to avoid zhuyijun
2017-11-14  1:42 ` no-reply

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=db7ef4f4-f95e-bb45-0a1a-5c40ca186956@redhat.com \
    --to=eric.auger@redhat.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 \
    --cc=zhuyijun@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).