From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: <iommu@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <kim.naru@amd.com>,
<jay.cornwall@amd.com>
Subject: Re: [PATCH] iommu/amd: Take mmap_sem when calling get_user_pages
Date: Tue, 6 May 2014 14:11:37 -0500 [thread overview]
Message-ID: <536933E9.6040404@amd.com> (raw)
In-Reply-To: <20140506181438.GD12376@8bytes.org>
On 5/6/2014 1:14 PM, Joerg Roedel wrote:
> On Mon, Apr 28, 2014 at 05:27:46PM -0500, Suthikulpanit, Suravee wrote:
>> From: Jay Cornwall <jay.cornwall@amd.com>
>>
>> get_user_pages requires caller to hold a read lock on mmap_sem.
>
> Right, but can't we just switch to get_user_pages_fast instead?
>
>
> Joerg
>
You're right. I think it can. Let me spin out another patch.
Suravee
next prev parent reply other threads:[~2014-05-06 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 22:27 [PATCH] iommu/amd: Take mmap_sem when calling get_user_pages suravee.suthikulpanit
2014-05-06 18:14 ` Joerg Roedel
2014-05-06 19:11 ` Suravee Suthikulanit [this message]
2014-05-06 19:27 ` Suravee Suthikulanit
2014-05-12 19:04 ` Joerg Roedel
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=536933E9.6040404@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jay.cornwall@amd.com \
--cc=joro@8bytes.org \
--cc=kim.naru@amd.com \
--cc=linux-kernel@vger.kernel.org \
/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