Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp4010403ybl; Mon, 26 Aug 2019 04:10:47 -0700 (PDT) X-Google-Smtp-Source: APXvYqz8w+LGG6aaORPujGLnacd6HDRP/714qCVDdMqUT693y9EJRBOfTQMEomVPx9Dm8Lc0cqU0 X-Received: by 2002:a17:90a:3465:: with SMTP id o92mr18909978pjb.20.1566817847517; Mon, 26 Aug 2019 04:10:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566817847; cv=none; d=google.com; s=arc-20160816; b=xvCMuN4/8G31HdyAJoWUPfAmskics6gHiLJ3C5sBY6LqAToHYrV/ntv8bczWE8ZAGO WwzBcuIIDhtxU51IRhVs17DEnjPB16OrA8lgKRBAzKVVUjtdkGdgvp/9YL7/foI6EnX4 J6J9vyvvxhNTvg5qWMn3LAeOwIvq9h9NsrgGglwdPM2RDEhUUzBKCL1v6HolutJpRuSw TczUzyTgpAKwhOWv1mk0Urrt21oohUmzWMx4HCG8gushpBFiqUUmdb1tN6Ht5+MPAA0S lFORtuQ+WoaejSZX2E4eP8YwgpRZmdQQkCVQnk2DYZ6yzrHCgiEfv3atBC4mTMRyQ6ai 5p8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:cc; bh=oHAWYsYx1csj4ieL1k+PVH9EJvJpiUXx75OjevcxOvM=; b=xEFqv4HvqcMfqk/TbeuLMa6Wh3vdvkPP+RUAxmEbVJPeD3iPgBbUuDjaE/hPzkKNhT mMMGn4PobRLR4hDUK9ALC9MIdGOdDOGpqNdlt85N34p6nj18/YwX7atefqX4bE+mE6Xg 5nb7uNpmoS2QM2hVuvR3CwoTr8cTXcn6wSEOtvpyR5asdDtBCXbWlBCGjSbwPFe8HCUH kqEgao2tO0cZqgCxoBI0lo4o0o/iST905Cm134IcKVn+W/OvJZFJe1uc/l1wRUWBJl+0 biwsTE1bCrjtGAijssieL07dGHdxxRXG1szT3ZE0bRerIc3sSRxJR0nb/PM1qZNfwfg5 78ig== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v11si9386845plg.31.2019.08.26.04.10.29; Mon, 26 Aug 2019 04:10:47 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730575AbfHZIa2 (ORCPT + 99 others); Mon, 26 Aug 2019 04:30:28 -0400 Received: from mga11.intel.com ([192.55.52.93]:46936 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729328AbfHZIa2 (ORCPT ); Mon, 26 Aug 2019 04:30:28 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Aug 2019 01:30:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,431,1559545200"; d="scan'208";a="379573481" Received: from allen-box.sh.intel.com (HELO [10.239.159.136]) ([10.239.159.136]) by fmsmga005.fm.intel.com with ESMTP; 26 Aug 2019 01:30:26 -0700 Cc: baolu.lu@linux.intel.com, David Woodhouse , Joerg Roedel , iommu@lists.linux-foundation.org, intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, =?UTF-8?Q?Micha=c5=82_Wajdeczko?= Subject: Re: [RFC PATCH] iommu/vt-d: Fix IOMMU field not populated on device hot re-plug To: Janusz Krzysztofik References: <20190822142922.31526-1-janusz.krzysztofik@linux.intel.com> <00f1a3a7-7ff6-e9a0-d9de-a177af6fd64b@linux.intel.com> <7536805.yzB8ZXLclH@jkrzyszt-desk.ger.corp.intel.com> From: Lu Baolu Message-ID: <790a4a20-7517-fe54-177d-850b9beeb88e@linux.intel.com> Date: Mon, 26 Aug 2019 16:29:12 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <7536805.yzB8ZXLclH@jkrzyszt-desk.ger.corp.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Janusz, On 8/26/19 4:15 PM, Janusz Krzysztofik wrote: > Hi Lu, > > On Friday, August 23, 2019 3:51:11 AM CEST Lu Baolu wrote: >> Hi, >> >> On 8/22/19 10:29 PM, Janusz Krzysztofik wrote: >>> When a perfectly working i915 device is hot unplugged (via sysfs) and >>> hot re-plugged again, its dev->archdata.iommu field is not populated >>> again with an IOMMU pointer. As a result, the device probe fails on >>> DMA mapping error during scratch page setup. >>> >>> It looks like that happens because devices are not detached from their >>> MMUIO bus before they are removed on device unplug. Then, when an >>> already registered device/IOMMU association is identified by the >>> reinstantiated device's bus and function IDs on IOMMU bus re-attach >>> attempt, the device's archdata is not populated with IOMMU information >>> and the bad happens. >>> >>> I'm not sure if this is a proper fix but it works for me so at least it >>> confirms correctness of my analysis results, I believe. So far I >>> haven't been able to identify a good place where the possibly missing >>> IOMMU bus detach on device unplug operation could be added. >> >> Which kernel version are you testing with? Does it contain below commit? >> >> commit 458b7c8e0dde12d140e3472b80919cbb9ae793f4 >> Author: Lu Baolu >> Date: Thu Aug 1 11:14:58 2019 +0800 > > I was using an internal branch based on drm-tip which didn't contain this > commit yet. Fortunately it has been already merged into drm-tip over last > weekend and has effectively fixed the issue. Thanks for testing this. Best regards, Lu Baolu