[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a7f1c69a-bbaf-4263-b2c2-3c92d65522c2@nvidia.com>
Date: Fri, 5 Jul 2024 22:53:06 +0000
From: Chaitanya Kulkarni <chaitanyak@...dia.com>
To: Christoph Hellwig <hch@....de>, Leon Romanovsky <leon@...nel.org>
CC: Jens Axboe <axboe@...nel.dk>, Jason Gunthorpe <jgg@...pe.ca>, Robin Murphy
<robin.murphy@....com>, Joerg Roedel <joro@...tes.org>, Will Deacon
<will@...nel.org>, Keith Busch <kbusch@...nel.org>, "Zeng, Oak"
<oak.zeng@...el.com>, Chaitanya Kulkarni <chaitanyak@...dia.com>, Sagi
Grimberg <sagi@...mberg.me>, Bjorn Helgaas <bhelgaas@...gle.com>, Logan
Gunthorpe <logang@...tatee.com>, Yishai Hadas <yishaih@...dia.com>, Shameer
Kolothum <shameerali.kolothum.thodi@...wei.com>, Kevin Tian
<kevin.tian@...el.com>, Alex Williamson <alex.williamson@...hat.com>, Marek
Szyprowski <m.szyprowski@...sung.com>, Jérôme Glisse
<jglisse@...hat.com>, Andrew Morton <akpm@...ux-foundation.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>, "linux-mm@...ck.org"
<linux-mm@...ck.org>
Subject: Re: [RFC PATCH v1 00/18] Provide a new two step DMA API mapping API
On 7/3/24 07:35, Christoph Hellwig wrote:
> On Wed, Jul 03, 2024 at 01:52:53PM +0300, Leon Romanovsky wrote:
>> On Wed, Jul 03, 2024 at 07:42:38AM +0200, Christoph Hellwig wrote:
>>> I just tried to boot this on my usual qemu test setup with emulated
>>> nvme devices, and it dead-loops with messages like this fairly late
>>> in the boot cycle:
>>>
>>> [ 43.826627] iommu: unaligned: iova 0xfff7e000 pa 0x000000010be33650 size 0x1000 min_pagesz 0x1000
>>> [ 43.826982] dma_mapping_error -12
>>>
>>> passing intel_iommu=off instead of intel_iommu=on (expectedly) makes
>>> it go away.
>> Can you please share your kernel command line and qemu?
>> On my and Chaitanya setups it works fine.
> qemu-system-x86_64 \
> -nographic \
> -enable-kvm \
> -m 6g \
> -smp 4 \
> -cpu host \
> -M q35,kernel-irqchip=split \
> -kernel arch/x86/boot/bzImage \
> -append "root=/dev/vda console=ttyS0,115200n8 intel_iommu=on" \
> -device intel-iommu,intremap=on \
> -device ioh3420,multifunction=on,bus=pcie.0,id=port9-0,addr=9.0,chassis=0 \
> -blockdev driver=file,cache.direct=on,node-name=root,filename=/home/hch/images/bookworm.img \
> -blockdev driver=host_device,cache.direct=on,node-name=test,filename=/dev/nvme0n1p4 \
> -device virtio-blk,drive=root \
> -device nvme,drive=test,serial=1234
>
I tried to reproduce this issue somehow it is not reproducible.
I'll try again on Leon's setup on my Saturday night, to fix that
case.
-ck
Powered by blists - more mailing lists