From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9A089A0547; Wed, 27 Oct 2021 08:46:23 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1BE0040DDA; Wed, 27 Oct 2021 08:46:23 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 2713D407FF for ; Wed, 27 Oct 2021 08:46:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1635317181; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ZT+J6OZyzJA4/x0UPC6Cqx9kTmXIjAIKaNifhg5wOrE=; b=ENcg4Hb3g6W/tmRuYM5Fc8TlOJ8SVpzzZW1opo8RuFrQ8lJxE2LN790+OiVre8H3mG+wKV yf08ehKlpe6k/EzxmLRA91EkMlviGRxIRjM5QdLOHyoNrNZQb122F/gsRCyHm/oVznW3O4 Q15KUKZpdHn2+44mxIb9iYfq9ma+PxI= Received: from mail-lf1-f72.google.com (mail-lf1-f72.google.com [209.85.167.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-586--0_vVPkuPEO635y5JDOiVA-1; Wed, 27 Oct 2021 02:46:18 -0400 X-MC-Unique: -0_vVPkuPEO635y5JDOiVA-1 Received: by mail-lf1-f72.google.com with SMTP id k15-20020a05651239cf00b003fe1ba9c94cso955144lfu.6 for ; Tue, 26 Oct 2021 23:46:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZT+J6OZyzJA4/x0UPC6Cqx9kTmXIjAIKaNifhg5wOrE=; b=aGNSZfCHJpLQMF7ExYQ2E3W/TTQCPkomj5BzQ/3qUvW7trau6f7x7NIg3bR+eJF1gc 3hJouKVLm6oMGVPyWJoYT8oRXjoAqng3TwU0gf9amu1a4f8Bx0iSF/JvozZ2wMyONgs6 MZ9F5F4ycJCzlJRtJI+vKiuynFIrHz3mH74OKjyIeCNNMV6wDmw4PqrB1tJ/xE0ApMAX Ekkj5+oO7oheu2sxeDL+n+SEKEUW2amKOGuYgRyQdEzpBWyIfWZFYLl6PprkFiLzDYe5 VbDP+rCil7TuRavvvkB3L8dR3yn9jTxgRMu9Cro2FGfvlQ9GFyzgX6xecdfAZHOOiC5d 3dRw== X-Gm-Message-State: AOAM530cAANIaNnGX83FnBYCvORqJsOB6f51NLMvLrABnurjuMDvp+2Q W5eU2XD8MZdwTRupCUPvnk6BWw9lBrW06Z7sAk+RfseZXLVxl8RW7IAyv0DtU9LZGQNCqzj0Bj3 bRWUBYRQ3CpHpu5T1g+w= X-Received: by 2002:ac2:4d56:: with SMTP id 22mr14097637lfp.265.1635317176850; Tue, 26 Oct 2021 23:46:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxXxCV+CcZbV8zRa1tGjwrjyB+gYB35fNWjSVPobk3ZFm1ZRlXRDyYfYXa5ZSiTe/RAR3o/gGm1FrvwLalob98= X-Received: by 2002:ac2:4d56:: with SMTP id 22mr14097614lfp.265.1635317176621; Tue, 26 Oct 2021 23:46:16 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Wed, 27 Oct 2021 08:46:05 +0200 Message-ID: To: fwefew 4t4tg <7532yahoo@gmail.com>, Marcin Wojtas , Michal Krawczyk , Shai Brandes , Evgeny Schemeilin , Igor Chauskin Cc: dev , Thomas Monjalon , "Yigit, Ferruh" Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] AWS i3.metal and IOMMU X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, Oct 27, 2021 at 2:55 AM fwefew 4t4tg <7532yahoo@gmail.com> wrote: > > As per https://doc.dpdk.org/guides/nics/ena.html section 17.9 > enabling IOMMU on an AWS i3 metal instance is as simple as adding "iommu=1 > intel_iommu=on" to /etc/default/grub, update-grub, and reboot. > > I can't get this to work. Once done, I cannot ssh back into the instance; > EC2 console can't get good status checks. It has to be terminated. My > config: > > * Ubuntu 20.04 LTS x86 64-bit stock AWS AMI > * i3.metal (spot) > > But more importantly: if one has provisioned a i3.metal instance, why > enable IOMMU at all? Can't one just run vfio-pci in > enable_unsafe_noiommu_mode? > > Even if IOMMU runs in enable_unsafe_noiommu_mode, I'd like to reconfirm the > steps to make DPDK work on an AWS i3.metal instance. My steps are: > > * git clone https://github.com/amzn/amzn-drivers.git > * git clone git://dpdk.org/dpdk and checkout tag 'v19.11-rc4' > * in dpdk git am in the patches from amzn-drivers 19.11 userspace dir > * build dpdk with: make install T=x86_64-native-linuxapp-gcc > DESTDIR=/home/ubuntu/local > * then follow the instructions at > https://github.com/amzn/amzn-drivers/tree/master/userspace/dpdk/enav2-vfio-patch > to build and install an updated vfio kernel module > > Is that complete and correct? - Let's ask the ENA DPDK maintainers. They should know best. - While at it, what is the status of upstreaming this write combined support in vfio? I found a RFC from 2017, and did not find anything else. We are trying to stick to upstream support, so mentioning in DPDK a non upstream kernel patch is not cool. -- David Marchand