linux-kernel - Re: [PATCH 2/2] ACPI: add DMI info to enable OSI(Linux) on PRIMEQUEST

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080527101302.4bd49e6c.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Tue, 27 May 2008 10:13:02 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Pavel Machek <pavel@...e.cz>
Cc:	Taku Izumi <izumi.taku@...fujitsu.com>, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] ACPI: add DMI info to enable OSI(Linux) on
 PRIMEQUEST

On Mon, 26 May 2008 10:06:14 +0200
Pavel Machek <pavel@...e.cz> wrote:

> On Mon 2008-05-26 16:56:05, Taku Izumi wrote:
> >
> > Thank you for your response.
> >
> >>> This patch adds DMI info to enable OSI(Linux) on PRIMEQUEST.
> >>> (PRIMEQUEST is ia64 machine.)
> >>
> >> Why is it needed? Why needs your bios know whether it is Linux or BSD
> >> or whatver running?
> >
> >   For memory hotplug support.
> >   Memory hotplug doesn't work on PRIMEQUEST when OSI(Linux) is disabled.
> 
> So fix the BIOS: there's no reason why memory hotplug should not work
> on BSD or Windows...
> 									Pavel
IIRC, PrimeQuest doesn't support BSD ;)

It's not really for memory hotplug. The result of _OSI method (TOOS) is
used for PCI, EC driver's behavior, etc.. (on my box) 

BTW, PrimeQuest's firmware is designed in 2.6.18 age and _heavily_ tested under
_OSI("Linux") environments. So, the acpi layer which returns _OSI("Linux") 
is valid for PrimeQuest. I don't hear a major firmware update for
already-sold-hosts is scheduled.

Thanks,
-Kame

--
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/