From: Robin Holt <holt@sgi.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>,
Jack Steiner <steiner@sgi.com>, mike travis <travis@sgi.com>
Cc: Tony Luck <tony.luck@intel.com>, Thomas Meyer <thomas@m3y3r.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Julia Lawall <julia@diku.dk>
Subject: Re: Missing put_cpu() in arch/ia64/sn/kernel/sn2/sn_hwperf.c?
Date: Thu, 11 Aug 2011 05:58:29 -0500 [thread overview]
Message-ID: <20110811105829.GA11879@sgi.com> (raw)
In-Reply-To: <4E4372DD.6020603@redhat.com>
On Thu, Aug 11, 2011 at 08:12:45AM +0200, Jes Sorensen wrote:
> On 08/08/11 23:37, Tony Luck wrote:
> > On Mon, Aug 8, 2011 at 11:05 AM, Thomas Meyer <thomas@m3y3r.de> wrote:
> >> The function sn_hwperf_op_cpu() seems to miss a corresponding put_cpu().
> >>
> >> Or is this done in another function? I didn't find it.
> >
> > It would be hard to do it elsewhere - this function may not have done
> > a get_cpu() [in the cpu == SN_HWPERF_ARG_ANY_CPU case].
> >
> > The logic is a bit tortuous here ... perhaps simpler to split the tests
> > up. Does the attached patch look right?
>
> Hi Tony,
>
> You probably want someone from SGI to look at it, so I'll forward to
> Robin Holt.
>
> I haven't been at SGI for about 2 years now :)
And I will bounce the question on to Jack. I believe he will probably
pass it on to somebody more familiar with sn_hwperf. Tony's patch looks
much clearer to me. I would have answered that I thought this was the
right patch until I saw the '... else { put_cpu(); ...' which made me
think we need a closer look.
Thanks,
Robin
next prev parent reply other threads:[~2011-08-11 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 18:05 Missing put_cpu() in arch/ia64/sn/kernel/sn2/sn_hwperf.c? Thomas Meyer
2011-08-08 21:37 ` Tony Luck
2011-08-11 6:12 ` Jes Sorensen
2011-08-11 10:58 ` Robin Holt [this message]
2011-08-11 13:59 ` Jack Steiner
2011-08-13 7:37 ` Thomas Meyer
2011-08-20 4:04 ` Mike Frysinger
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=20110811105829.GA11879@sgi.com \
--to=holt@sgi.com \
--cc=Jes.Sorensen@redhat.com \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
--cc=thomas@m3y3r.de \
--cc=tony.luck@intel.com \
--cc=travis@sgi.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 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.