lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1268751800.2671.16.camel@zim>
Date:	Tue, 16 Mar 2010 09:03:20 -0600
From:	Myron Stowe <myron.stowe@...com>
To:	ykzhao <yakui.zhao@...el.com>
Cc:	"minyard@....org" <minyard@....org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"openipmi-developer@...ts.sourceforge.net" 
	<openipmi-developer@...ts.sourceforge.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"lenb@...nel.org" <lenb@...nel.org>
Subject: Re: [PATCH v2 1/3] ipmi: Raise precedence of PNP based discovery
 mechanisms (ACPI, PCI)

On Mon, 2010-03-15 at 09:48 +0800, ykzhao wrote:
> On Sun, 2010-03-14 at 02:13 +0800, Myron Stowe wrote:
> > This raises the precedence of PNP discovery mechanisms, ACPI and  PCI,
> > above SMBIOS and SPMI as indicated by Appendix C1 of the IPMI
> > specification.
> > 
> > Reference: IPMI - Intelligent Platform Management Interface Specification
> >            v2.0, Document Revision 1.0, 05.05.2005 Markup
> > 
> >   Appendix C1 - Locating IPMI System Interfaces via SMBIOS Tables
> >       "Note that the settings that this structure reports may be over-
> >       ridden by `Plug-and-Play' reassignment by the OS.  Therefore, this
> >       structure should be used only when the interface cannot be
> >       discovered via `Plug-and-Play' discovery mechanisms incorporated
> >       in interfaces such as PCI and ACPI."
> 
> Hi,
>     The SPMI detection mechanism belongs to one of two ACPI detection
> mechanisms.  Can we put it before DMI detection mechanism?

The SPMI detection method is similar to the DMI (SMBIOS) in that they
are both static tables and thus should be after methods capable of
changes from OS reassignment.

The order between these two probably does not make a great deal of
difference.  The logic I used was to maintain the original order, just
copy and paste, which kept SPMI after SMBIOS which also seemed natural
since SMBIOS is older, a possible indication that it is the more widely
used method of the two.

Myron

>     
>     Anyway, it is right that the pnp discovery mechanism has higher
> priority than PCI/SPMI/SMBIOS.
> 
> Thanks.
>    Yakui
> > 
> > Signed-off-by: Myron Stowe <myron.stowe@...com>
> > ---
> > 
> >  drivers/char/ipmi/ipmi_si_intf.c |   15 ++++++++-------
> >  1 files changed, 8 insertions(+), 7 deletions(-)
> > 
> > diff --git a/drivers/char/ipmi/ipmi_si_intf.c b/drivers/char/ipmi/ipmi_si_intf.c
> > index 176f175..86a7dd7 100644
> > --- a/drivers/char/ipmi/ipmi_si_intf.c
> > +++ b/drivers/char/ipmi/ipmi_si_intf.c
> > @@ -3197,13 +3197,6 @@ static __devinit int init_ipmi_si(void)
> >  
> >  	hardcode_find_bmc();
> >  
> > -#ifdef CONFIG_DMI
> > -	dmi_find_bmc();
> > -#endif
> > -
> > -#ifdef CONFIG_ACPI
> > -	spmi_find_bmc();
> > -#endif
> >  #ifdef CONFIG_ACPI
> >  	pnp_register_driver(&ipmi_pnp_driver);
> >  #endif
> > @@ -3220,6 +3213,14 @@ static __devinit int init_ipmi_si(void)
> >  	of_register_platform_driver(&ipmi_of_platform_driver);
> >  #endif
> >  
> > +#ifdef CONFIG_DMI
> > +	dmi_find_bmc();
> > +#endif
> > +
> > +#ifdef CONFIG_ACPI
> > +	spmi_find_bmc();
> > +#endif
> > +
> >  	if (si_trydefaults) {
> >  		mutex_lock(&smi_infos_lock);
> >  		if (list_empty(&smi_infos)) {
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> > the body of a message to majordomo@...r.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


-- 
Myron Stowe                             HP Open Source Linux Lab (OSLL)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ