From: Greg KH <gregkh@suse.de>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'devel@driverdev.osuosl.org'" <devel@driverdev.osuosl.org>,
"'virtualization@lists.osdl.org'" <virtualization@lists.osdl.org>,
Hank Janssen <hjanssen@microsoft.com>
Subject: Re: [PATCH 1/1] staging: hv: Fix race condition on IC channel initialization (modified)
Date: Thu, 27 May 2010 16:22:32 -0700 [thread overview]
Message-ID: <20100527232232.GA15341@suse.de> (raw)
In-Reply-To: <1FB5E1D5CA062146B38059374562DF7266B8C7C4@TK5EX14MBXC128.redmond.corp.microsoft.com>
On Wed, May 26, 2010 at 10:52:36PM +0000, Haiyang Zhang wrote:
> > From: Greg KH [mailto:gregkh@suse.de]
> > How about a lock!
> >
> > What's so scary about a pretty little semaphore? They are all cute and
> > cuddley and don't bite anyone. You should not be afraid to use them,
> > they are here to do your bidding.
>
> No problem, we will add a lock here.
>
> > > The VmbusChannelProcessOffer() is called from interrupt context, and
> > > initialize the channels, wake up vmbus_init when all channels are
> > > ready. If using local variable only, how to pass the channel ready
> > > info to vmbus_init() which is in a different context?
> >
> > No, I mean move the logic you added here, into the vmbus_init() call.
>
> Do you mean:
> Move the event creat/wait/free, which is currently in vmbus_init(),
> into vmbus_bus_init() function.
Yes.
> hv_channle_ready will still be a global variable.
That's fine.
> And, the wakeup call -- osd_WaitEventSet() --remains in
> VmbusChannelProcessOffer() ?
Yes.
And as Jiri pointed out, this should be a simple completion.
thanks,
greg k-h
next prev parent reply other threads:[~2010-05-27 23:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 16:54 [PATCH 1/1] staging: hv: Fix race condition on IC channel initialization (modified) Haiyang Zhang
2010-05-26 20:51 ` Greg KH
2010-05-26 21:25 ` Haiyang Zhang
2010-05-26 21:48 ` Greg KH
2010-05-26 22:03 ` Hank Janssen
2010-05-26 22:03 ` Hank Janssen
2010-05-26 22:23 ` Haiyang Zhang
2010-05-26 22:30 ` Greg KH
2010-05-26 22:30 ` Greg KH
2010-05-26 22:52 ` Haiyang Zhang
2010-05-27 23:22 ` Greg KH [this message]
2010-05-27 6:16 ` Jiri Slaby
-- strict thread matches above, loose matches on Subject: below --
2010-05-26 16:54 Haiyang Zhang
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=20100527232232.GA15341@suse.de \
--to=gregkh@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.