From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 6B84B5B3E for ; Mon, 21 Jan 2019 15:45:01 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id CCBE42689A; Mon, 21 Jan 2019 09:44:58 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 21 Jan 2019 09:44:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=4pkzF7UBoW+wh3OZyxCTtUw7cbHbHEH0Ae1j8Vk4+2o=; b=BieIzAl6LjDs df91Q/DaMN07ebffcZuaH2ubg4pRei2iMFCiYiCw6IDxY8bosJ/63tUqsTkUXs+g 9AkB2ANYzCbH9s/c6NiwZ5DvjyrL2jP3Ji9Nd8gkiKtJADb2/rvUSlfWw0UM7VPf lyNw1Tj36xhkd514FBphw0Xkmtd2FC8= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=4pkzF7UBoW+wh3OZyxCTtUw7cbHbHEH0Ae1j8Vk4+ 2o=; b=QJQhWbywsvzldNYG4sGnQjRVsJmqooRAByagTpoiOY+zUy4Pm0CN0Js4H D/EHcdzZbOISpiXem6eruJ2Cu/s/gIq6BB2zY8/yMFA1P512ghqdX/fYDRhFwzQZ eOIQxlllBg8WqAfDMHaXm23XMLlRc0I+SMPBIEpfwN06tpg+qNg2X8pyX/OsTUah hTvuQo/DttXdx/6WibHFMO8ydL20bjrlu0V9mX/kGYANP3lZHGHUmywRE7Q0GhRy nmHMIxDN2rzB1w4anIZGHcXEfdk2LiQcLA39+GCjSljp63yprT0dvp/hafykQUvt 2pFmP35wtgYirybs8PgFOfp6Xgi+w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrheeigdeilecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkfgjfh gggfgtsehtqhertddttdejnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceo thhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuffhomhgrihhnpeguphgukhdroh hrghenucfkphepjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivg eptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B514D100E5; Mon, 21 Jan 2019 09:44:57 -0500 (EST) From: Thomas Monjalon To: "Burakov, Anatoly" Cc: "Hu, Xuekun" , Ravi Kerur , "dev@dpdk.org" , "Ananyev, Konstantin" , "Lu, Wenzhuo" Date: Mon, 21 Jan 2019 15:44:55 +0100 Message-ID: <81479048.sikF43hQBL@xps> In-Reply-To: References: <88A92D351643BA4CB23E30315517062663547499@SHSMSX103.ccr.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" 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: Mon, 21 Jan 2019 14:45:01 -0000 21/01/2019 14:39, Burakov, Anatoly: > On 21-Jan-19 1:18 PM, Hu, Xuekun wrote: > >=20 > >> You might also want to look here: https://bugs.dpdk.org/show_bug.cgi?i= d=3D76 > >=20 > >> There are apparently issues with some kernel versions that will manife= st themselves as problems with using VF devices with IOMMU in a VM. > >=20 > > Thanks, Anatoly. By updating host kernel to 4.18, the issue is gone. = =F0=9F=98=8A > >=20 >=20 > @Thomas, does this look like something we should add to known issues?=20 > This question has been asked a few times already. Yes sure