From: Michael Ellerman <michael@ellerman.id.au>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] pseries: asm/pci-bridge.h CONFIG_ minor cleanup
Date: Wed, 23 May 2007 11:11:32 +1000 [thread overview]
Message-ID: <1179882692.6145.8.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <20070522170058.GJ5921@austin.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On Tue, 2007-05-22 at 12:00 -0500, Linas Vepstas wrote:
> On Tue, May 22, 2007 at 10:40:59AM +1000, Michael Ellerman wrote:
> > On Mon, 2007-05-21 at 18:18 -0500, Linas Vepstas wrote:
> > > Use the correct CONFIG_ option to mark off the EEH bits.
> >
> > You're making the struct 4 bytes larger by creating a hole here :(
>
> Hmm. Perhaps I could shuffle one of the ints down ...
>
> I figured there might be some vague cache-line benefits to
> getting the eeh stuff out of the way.
Yeah who knows. The hole doesn't really matter unless the struct gets
bigger, having the EEH stuff at the bottom makes it read better which is
probably more important.
> > > u32 config_space[16]; /* saved PCI config space */
> > > +#endif
> >
> > It looks correct, but I think it's worth mentioning in the changelog
> > that config_space was previously unconditionally defined, but is now
> > within CONFIG_EEH.
>
> I could just tell that someone would remark on this; why I didn't
> mention it, I don't know.
Me neither :)
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-23 1:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 23:18 [PATCH] pseries: asm/pci-bridge.h CONFIG_ minor cleanup Linas Vepstas
2007-05-22 0:40 ` Michael Ellerman
2007-05-22 17:00 ` Linas Vepstas
2007-05-22 18:18 ` [PATCH] (revised) " Linas Vepstas
2007-05-23 1:11 ` Michael Ellerman [this message]
2007-05-23 20:51 ` [PATCH] " Linas Vepstas
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=1179882692.6145.8.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).