From: Randy Dunlap <randy.dunlap@oracle.com>
To: Konrad Rzeszutek <konrad@darnok.org>
Cc: linux-kernel@vger.kernel.org, pjones@redhat.com,
konradr@redhat.com, konradr@linux.vnet.ibm.com
Subject: Re: [PATCH] Add iSCSI iBFT support.
Date: Wed, 26 Sep 2007 21:29:21 -0700 [thread overview]
Message-ID: <20070926212921.33e2e58d.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200709262052.44845.konrad@darnok.org>
On Wed, 26 Sep 2007 20:52:43 -0400 Konrad Rzeszutek wrote:
> > > +config ISCSI_IBFT
> > > + tristate "iSCSI Boot Firmware Table Attributes"
> > > + depends on X86
> >
> > why only on X86?
>
> PowerPC exports this data via the OpenFirmware so it already shows in
> the /sysfs entries. I was thinking to combine those sysfs entries under this
> code, but that is something in the future.
>
> In regards to all other platforms, I figured I would only make it supported
> under platforms that have been tested. Is there anything that stops this from
> working for example of IA64? Well no. The hardware that supports the iBFT is
> either in the BIOS or in NICs - so the SGI or HP boxes _should_ work, however
> I am not comfortable to make it supported unless I've tested it.
That's not how Linux development works. You (we) have a huge
test lab around the world. You practice "release early, release
often" and get testing/feedback on it. Maybe even patches. :)
> > Need blank line here... except why is this function in the header
>
> Fixed blank line.
> > file? and why is it inline?
>
> Q: "Why is this function in the header file"
> If the find_ibft() was to be implemented in firmware/iscsi_ibft.c code the
> firmware-driver couldn't be compiled as a module (or rather it could, but
> when the vmlinuz was to be linked it would complain about missing symbol -
> find_ibft). I was thinking to let the user give the choice whether they want
> to load this firmware driver or have it built-in the kernel.
>
> Q:"Why is it inline"
> Uhh. It does not need to. I will remove the 'inline' part.
But we strongly prefer not to have non-inline C code in header files,
[and the function does not need to be inline]
so find_ibft() needs a home in some source file/code that won't be built
as a loadable module, right? And preferably not duplicated (i386 &
x86_64 versions; but we should see a merged x86/ arch soon, so it
sounds). Would ia64 have its own version of find_ibft() or use this
same code?
I think that for now you can put find_ibft() in both setup.c files
and the merged x86/ arch tree can eliminate one of them.
On looking back at the patch, why aren't the ibft_phys and find_ibft()
parts of both setup.c patches surrounded by #ifdef CONFIG_ISCSI_IBFT &
#endif ?
---
~Randy
Phaedrus says that Quality is about caring.
next prev parent reply other threads:[~2007-09-27 4:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 18:46 [PATCH] Add iSCSI iBFT support Konrad Rzeszutek
2007-09-26 19:37 ` roel
2007-09-26 21:10 ` Greg KH
2007-09-27 0:08 ` Konrad Rzeszutek
2007-09-27 2:04 ` Greg KH
2007-09-26 21:13 ` Randy Dunlap
2007-09-27 0:16 ` Konrad Rzeszutek
2007-09-26 21:29 ` Randy Dunlap
2007-09-27 0:52 ` Konrad Rzeszutek
[not found] ` <14e4363b0709261817t5f0b1922m99c24549ce316de8@mail.gmail.com>
2007-09-27 4:00 ` Randy Dunlap
2007-09-27 4:29 ` Randy Dunlap [this message]
2007-09-27 17:06 ` H. Peter Anvin
2007-09-27 17:12 ` Peter Jones
2007-09-27 17:18 ` H. Peter Anvin
2007-09-27 17:51 ` Peter Jones
2007-09-27 20:50 ` Len Brown
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=20070926212921.33e2e58d.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=konrad@darnok.org \
--cc=konradr@linux.vnet.ibm.com \
--cc=konradr@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjones@redhat.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