From: Joerg Roedel <joro@8bytes.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: iommu@lists.linux-foundation.org,
Benjamin LaHaise <bcrl@kvack.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-aio@kvack.org, linux-kernel@vger.kernel.org,
Oded Gabbay <oded.gabbay@amd.com>,
jroedel@suse.de
Subject: Re: [PATCH] iommu/amd: Use wait_event in put_pasid_state_wait
Date: Wed, 4 Feb 2015 17:36:25 +0100 [thread overview]
Message-ID: <20150204163625.GP3702@8bytes.org> (raw)
In-Reply-To: <20150204163450.GD5029@twins.programming.kicks-ass.net>
On Wed, Feb 04, 2015 at 05:34:50PM +0100, Peter Zijlstra wrote:
> On Wed, Feb 04, 2015 at 04:10:22PM +0100, Joerg Roedel wrote:
> > From: Joerg Roedel <jroedel@suse.de>
> >
> > Now that I learned about possible spurious wakeups this
> > place needs fixing too. Replace the self-coded sleep variant
> > with the generic wait_event() helper.
> >
> > Signed-off-by: Joerg Roedel <jroedel@suse.de>
> > ---
> > drivers/iommu/amd_iommu_v2.c | 9 +--------
> > 1 file changed, 1 insertion(+), 8 deletions(-)
> >
> > diff --git a/drivers/iommu/amd_iommu_v2.c b/drivers/iommu/amd_iommu_v2.c
> > index b6398d7..5cc1409 100644
> > --- a/drivers/iommu/amd_iommu_v2.c
> > +++ b/drivers/iommu/amd_iommu_v2.c
> > @@ -266,14 +266,7 @@ static void put_pasid_state(struct pasid_state *pasid_state)
> >
> > static void put_pasid_state_wait(struct pasid_state *pasid_state)
> > {
> > - DEFINE_WAIT(wait);
> > -
> > - prepare_to_wait(&pasid_state->wq, &wait, TASK_UNINTERRUPTIBLE);
> > -
> > - if (!atomic_dec_and_test(&pasid_state->count))
> > - schedule();
> > -
> > - finish_wait(&pasid_state->wq, &wait);
> > + wait_event(pasid_state->wq, !atomic_read(&pasid_state->count));
> > free_pasid_state(pasid_state);
> > }
>
> You just lost your atomic_dec.
Right, thanks.
next prev parent reply other threads:[~2015-02-04 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 15:10 [PATCH] iommu/amd: Use wait_event in put_pasid_state_wait Joerg Roedel
2015-02-04 16:34 ` Peter Zijlstra
2015-02-04 16:36 ` Joerg Roedel [this message]
2015-02-05 11:40 ` [PATCH v2] " Joerg Roedel
2015-02-05 12:23 ` Oded Gabbay
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=20150204163625.GP3702@8bytes.org \
--to=joro@8bytes.org \
--cc=bcrl@kvack.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=jroedel@suse.de \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oded.gabbay@amd.com \
--cc=peterz@infradead.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