From: Christoph Hellwig <hch@lst.de>
To: boutcher@us.ibm.com, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] viopath: use completion
Date: Tue, 15 May 2007 15:10:34 +0200 [thread overview]
Message-ID: <20070515131034.GB11544@lst.de> (raw)
In-Reply-To: <20070513155027.GB9218@lst.de>
On Sun, May 13, 2007 at 05:50:27PM +0200, Christoph Hellwig wrote:
> Use a completion instead of abusing a semaphore for hypervisor event
> completion in viopath.
And some more of the same sort:
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: linux-2.6.20/arch/powerpc/platforms/iseries/viopath.c
===================================================================
--- linux-2.6.20.orig/arch/powerpc/platforms/iseries/viopath.c 2007-05-15 14:48:57.000000000 +0200
+++ linux-2.6.20/arch/powerpc/platforms/iseries/viopath.c 2007-05-15 14:51:36.000000000 +0200
@@ -81,7 +81,7 @@ static void handleMonitorEvent(struct Hv
* if system_state is not SYSTEM_RUNNING, then wait_atomic is used ...
*/
struct alloc_parms {
- struct semaphore sem;
+ struct completion done;
int number;
atomic_t wait_atomic;
int used_wait_atomic;
@@ -464,7 +464,7 @@ static void viopath_donealloc(void *parm
if (parmsp->used_wait_atomic)
atomic_set(&parmsp->wait_atomic, 0);
else
- up(&parmsp->sem);
+ complete(&parmsp->done);
}
static int allocateEvents(HvLpIndex remoteLp, int numEvents)
@@ -476,7 +476,7 @@ static int allocateEvents(HvLpIndex remo
atomic_set(&parms.wait_atomic, 1);
} else {
parms.used_wait_atomic = 0;
- init_MUTEX_LOCKED(&parms.sem);
+ init_completion(&parms.done);
}
mf_allocate_lp_events(remoteLp, HvLpEvent_Type_VirtualIo, 250, /* It would be nice to put a real number here! */
numEvents, &viopath_donealloc, &parms);
@@ -484,7 +484,7 @@ static int allocateEvents(HvLpIndex remo
while (atomic_read(&parms.wait_atomic))
mb();
} else
- down(&parms.sem);
+ wait_for_completion(&parms.done);
return parms.number;
}
@@ -585,10 +585,10 @@ int viopath_close(HvLpIndex remoteLp, in
spin_unlock_irqrestore(&statuslock, flags);
parms.used_wait_atomic = 0;
- init_MUTEX_LOCKED(&parms.sem);
+ init_completion(&parms.done);
mf_deallocate_lp_events(remoteLp, HvLpEvent_Type_VirtualIo,
numReq, &viopath_donealloc, &parms);
- down(&parms.sem);
+ wait_for_completion(&parms.done);
spin_lock_irqsave(&statuslock, flags);
for (i = 0, numOpen = 0; i < VIO_MAX_SUBTYPES; i++)
prev parent reply other threads:[~2007-05-15 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 15:50 [PATCH] viopath: use completion Christoph Hellwig
2007-05-14 0:44 ` Stephen Rothwell
2007-05-14 0:54 ` David Boutcher
2007-05-15 13:10 ` Christoph Hellwig [this message]
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=20070515131034.GB11544@lst.de \
--to=hch@lst.de \
--cc=boutcher@us.ibm.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).