From: Linas Vepstas <linas@austin.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org,
long <tlnguyen@snoqualmie.dp.intel.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Greg KH <greg@kroah.com>,
ak@muc.de, Paul Mackerras <paulus@samba.org>,
linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
linux-pci@atrey.karlin.mff.cuni.cz, johnrose@us.ibm.com
Subject: Re: [PATCH 8/13]: PCI Err: Event delivery utility
Date: Wed, 29 Jun 2005 19:29:36 -0500 [thread overview]
Message-ID: <20050630002936.GS28499@austin.ibm.com> (raw)
In-Reply-To: <1120088522.31924.25.camel@gaston>
On Thu, Jun 30, 2005 at 09:42:01AM +1000, Benjamin Herrenschmidt was heard to remark:
> On Wed, 2005-06-29 at 16:14 -0500, Linas Vepstas wrote:
>
> > I'm pretty sure this was balanced, there is a get very early on when the
> > error is detected. But I'll review.
> >
> > > I'd keep that in arch code for now.
> >
> > OK, I'm moving it there. It did seem both confusing and semi-pointless
> > after the last round of changes.
>
> Well, it's logical for the get and put to be in the same "layer" don't
> you think ?
Yes, it could be made more symmetrical; I'll do that.
The get happened along with the malloc of the event structure, the put
happens right before the free of the same structure.
The reason for the event was in order to get the recovery of the error
out of line from the detection of the error; detection may occur in an
interrupt context; recovery happens in a work queue. Thus, get may
happen in that interrupt context, the put only after the work is
complete.
I'll make the code more symmetrical with regards to the event malloc/free
and that should make it more readable.
--linas
prev parent reply other threads:[~2005-06-30 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 23:59 [PATCH 8/13]: PCI Err: Event delivery utility Linas Vepstas
2005-06-29 1:59 ` Benjamin Herrenschmidt
2005-06-29 21:14 ` Linas Vepstas
2005-06-29 23:42 ` Benjamin Herrenschmidt
2005-06-30 0:29 ` Linas Vepstas [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=20050630002936.GS28499@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=ak@muc.de \
--cc=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=johnrose@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tlnguyen@snoqualmie.dp.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox