public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Lu Baolu <baolu.lu@linux.intel.com>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: baolu.lu@linux.intel.com, "David Woodhouse" <dwmw2@infradead.org>,
	"Joerg Roedel" <joro@8bytes.org>,
	iommu@lists.linux-foundation.org,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	"Michał Wajdeczko" <michal.wajdeczko@intel.com>
Subject: Re: [RFC PATCH] iommu/vt-d: Fix IOMMU field not populated on device hot re-plug
Date: Mon, 26 Aug 2019 16:29:12 +0800	[thread overview]
Message-ID: <790a4a20-7517-fe54-177d-850b9beeb88e@linux.intel.com> (raw)
In-Reply-To: <7536805.yzB8ZXLclH@jkrzyszt-desk.ger.corp.intel.com>

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 <baolu.lu@linux.intel.com>
>> 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

  reply	other threads:[~2019-08-26  8:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22 14:29 [RFC PATCH] iommu/vt-d: Fix IOMMU field not populated on device hot re-plug Janusz Krzysztofik
2019-08-22 15:34 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-08-23  1:51 ` [RFC PATCH] " Lu Baolu
2019-08-26  8:15   ` Janusz Krzysztofik
2019-08-26  8:29     ` Lu Baolu [this message]
     [not found]       ` <790a4a20-7517-fe54-177d-850b9beeb88e-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2019-08-27  9:35         ` Janusz Krzysztofik
2019-08-28  0:56           ` Lu Baolu
2019-08-28 14:17             ` Janusz Krzysztofik
2019-08-29  1:43               ` Lu Baolu
2019-08-29  7:58                 ` Janusz Krzysztofik
2019-08-29  9:08                   ` Lu Baolu
2019-09-02  8:37                     ` Janusz Krzysztofik
2019-09-03  1:29                       ` Lu Baolu
2019-09-03  7:41                         ` Janusz Krzysztofik
2019-10-01 15:01                           ` Janusz Krzysztofik
     [not found]                             ` <7739498.9tyZrNxj5X-RCb3PieevP79BXuAQUXR0fooFf0ArEBIu+b9c/7xato@public.gmane.org>
2019-10-08  2:27                               ` Lu Baolu
2019-10-11  6:54                           ` Lu Baolu
2019-10-11 10:27                             ` Janusz Krzysztofik
2019-08-23  8:47 ` ✓ Fi.CI.IGT: success for " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=790a4a20-7517-fe54-177d-850b9beeb88e@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=janusz.krzysztofik@linux.intel.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.wajdeczko@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox