From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f50.google.com (mail-lf0-f50.google.com [209.85.215.50]) by dpdk.org (Postfix) with ESMTP id D6F192BBD for ; Thu, 1 Feb 2018 20:26:30 +0100 (CET) Received: by mail-lf0-f50.google.com with SMTP id k19so27965696lfj.1 for ; Thu, 01 Feb 2018 11:26:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FE/ZnEf2QGWT8wNcnhtGlpEiUmQNq+Cza7rcZLEHnnI=; b=EDiwF1OhmKEBKcqjGorFn4WkNsjqk9380LdeEKK/cLWX8s0JdvYGo3oATsgdWUbS34 g2ul3tyeZCDP0Jslwxcvfk1hnfgFbs7jBGoASsXUL1A5qymAe/nhtHgnPl3rFVufIFO0 1pwLBs5CiAFJ//Goles8ADyv/0l7z+ylzKJv8LNVr3HY1pWxEXaQ+a69njdr7a0CYIK6 LtMdb7ImwrHPrLz11kUd4Wv6igv7BaaJA5Tw/LxzZaQ5TlVJcWQ7HfFfQhdsXSzSCq1G GJ+P6yjR3VggpCwcRbPxfQOkOmlIJzRHzdHevLvdj7wiHxfMiR3i9CTjC+lCAh9ARCo3 3JDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FE/ZnEf2QGWT8wNcnhtGlpEiUmQNq+Cza7rcZLEHnnI=; b=Duvmf4SvCqUQ0Pcfh9q8VY4I67KT362lVwUKQ+X3/p76zfz/TQev5tGgNvOUrzFBfV Y60y/OuZPTSgEcZ1nxuifBc/ZHlIwYOTM8vmsZbQnhotv2q4ujm0EUk5byGShAAxlVUt 1N+30BarrUlHaH7ea6b36HFvxAlzeBYLrXRaX3mE0zAJAr8962+EeaijqIylonJAEaE1 eHrRrCpGg3S0GIsL0FRVNNaw7AFlDzvNfN+SDNvQxn1r1250IRE1xEYtRwiZ3MW+aWwQ UhO7nIHyyRVMVM2CYRFnd8pgs4ZsHrgGBz26Vo15+zKuSJzm2czN++DRwlt22sWVDZnl /w0A== X-Gm-Message-State: AKwxytdFa34D/V4Lj07JYG5N/n6LQiPWa0YRzHyl8/ANKjK//BT3iyco pgZsqRDM5lSp6ybbtdCiJ9A7kIsgPz9MC+dAbco= X-Google-Smtp-Source: AH8x226Zr1HomdcnUmebIL92nbN8mVMUJ+r9KHDYdCZ8DiMdlEu5oDbvEq5kPD0dVBc6L9gTy5RP29Ew7U3n+eiyl1M= X-Received: by 10.46.4.196 with SMTP id a65mr10633704ljf.22.1517513190348; Thu, 01 Feb 2018 11:26:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.196.17 with HTTP; Thu, 1 Feb 2018 11:26:29 -0800 (PST) In-Reply-To: <3464b900-8648-c128-e959-dc60a8883a2d@intel.com> References: <8ddb30a3-1253-ff60-20bb-b735fef5a91c@intel.com> <10911b54-57ee-370b-a4f7-f34accf4811e@intel.com> <3464b900-8648-c128-e959-dc60a8883a2d@intel.com> From: Ravi Kerur Date: Thu, 1 Feb 2018 11:26:29 -0800 Message-ID: To: "Burakov, Anatoly" Cc: dev@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] IXGBE, IOMMU DMAR DRHD handling fault issue X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 19:26:31 -0000 On Thu, Feb 1, 2018 at 2:10 AM, Burakov, Anatoly wrote: > On 31-Jan-18 9:51 PM, Ravi Kerur wrote: > >> >> Hi Anatoly, >> >> Thanks. I am following wiki link below which uses vIOMMU with DPDK as a >> use-case and instantiate VM as specified with Q35 chipset in Qemu. >> >> https://wiki.qemu.org/Features/VT-d >> >> Qemu-version is 2.11 >> Host kernel 4.9 >> Guest kernel 4.4 >> >> I can only guess that guest kernel needs an upgrade in my setup to work >> correctly, if versions on my setup rings a bell on not having support >> kindly let me know. >> >> When 'modprobe vfio enable_unsafe_noiommu_node=Y' is executed on guest I >> get following error >> ... >> vfio: unknown parameter 'enable_unsafe_noiommu_node' ignored >> ... >> >> in guest. >> >> Thanks. >> > > AFAIK kernel 4.4 should have noiommu mode - it was introduced in 3.1x days. > However, in order for that to work, kernel also has to be built with this > mode enabled. My guess is, whoever is the supplier of your kernel, did not > do that. You should double-check the kernel configuration of your > distribution. > > However, if you have vIOMMU in QEMU, you shouldn't need noiommu mode - > "regular" vfio should work fine. noiommu mode should only be needed if you > know you don't have IOMMU enabled in your kernel, and even if you can't > enable it, you can still use igb_uio. > > Hi Anatoly, Do you suggest I take this discussion to kvm/qemu mailing list as I am not sure which component has the issue? I check dmesg for BIOS physical memory map and address reported as fault by DMAR is reported by BIOS as usable on both host and vm. [ 4539.597737] DMAR: [DMA Read] Request device [04:10.0] fault addr *33a128000 *[fault reason 06] PTE Read access is not set dmesg | grep BIOS [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009afff] usable [ 0.000000] BIOS-e820: [mem 0x000000000009b000-0x000000000009ffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007938afff] usable [ 0.000000] BIOS-e820: [mem 0x000000007938b000-0x000000007994bfff] reserved [ 0.000000] BIOS-e820: [mem 0x000000007994c000-0x000000007999cfff] ACPI data [ 0.000000] BIOS-e820: [mem 0x000000007999d000-0x0000000079f7dfff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x0000000079f7e000-0x000000007bd37fff] reserved [ 0.000000] BIOS-e820: [mem 0x000000007bd38000-0x000000007bd38fff] usable [ 0.000000] BIOS-e820: [mem 0x000000007bd39000-0x000000007bdbefff] reserved [ 0.000000] BIOS-e820: [mem 0x000000007bdbf000-0x000000007bffffff] usable [ 0.000000] BIOS-e820: [mem 0x000000007c000000-0x000000008fffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed44fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved [* 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000407fffffff] usable* Kindly let me know your inputs. Thanks. -- > Thanks, > Anatoly >