linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Yinghai Lu <yinghai.lu@oracle.com>, Kalle Valo <kvalo@adurom.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pci, dmar: flush IOTLB before exit domain
Date: Mon, 09 May 2011 13:56:57 -0700	[thread overview]
Message-ID: <4DC85519.8020303@kernel.org> (raw)
In-Reply-To: <1304952530.30435.16.camel@i7.infradead.org>

On 05/09/2011 07:48 AM, David Woodhouse wrote:
> On Thu, 2011-05-05 at 18:13 -0700, Yinghai Lu wrote:
>> @@ -3252,6 +3252,9 @@ static int device_notifier(struct notifi
>>                 return 0;
>>  
>>         if (action == BUS_NOTIFY_UNBOUND_DRIVER && !iommu_pass_through) {
>> +               /* before we remove dev with domain, flush IOTLB */
>> +               flush_unmaps();
>> +
>>                 domain_remove_one_dev_info(domain, pdev);
>>  
>>                 if (!(domain->flags & DOMAIN_FLAG_VIRTUAL_MACHINE) && 
> 
> That calls flush_unmaps() without the async_umap_flush_lock held,
> doesn't it? A few days ago I asked someone else to test this candidate
> patch for a similar issue:
> 
> http://david.woodhou.se/flush-unmaps-on-unbind.patch
> 

Your patch works.

Thanks

Yinghai

  reply	other threads:[~2011-05-09 20:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06  1:13 [PATCH] pci, dmar: flush IOTLB before exit domain Yinghai Lu
2011-05-09 14:48 ` David Woodhouse
2011-05-09 20:56   ` Yinghai Lu [this message]
2011-05-16 15:13   ` Alex Williamson
2011-05-17 19:41     ` Alex Williamson
2011-05-18  1:57       ` Alex Williamson
2011-05-21 14:38         ` Jan Kiszka
2011-05-24 11:04         ` Woodhouse, David
2011-05-24 16:29           ` Alex Williamson

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=4DC85519.8020303@kernel.org \
    --to=yinghai@kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kvalo@adurom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=yinghai.lu@oracle.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;
as well as URLs for NNTP newsgroup(s).