From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Zachary Amsden <zach@vmware.com>, Andrew Morton <akpm@osdl.org>,
Chris Wright <chrisw@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Martin Bligh <mbligh@mbligh.org>,
Pratap Subrahmanyam <pratap@vmware.com>,
Christopher Li <chrisl@vmware.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH 14/21] i386 Apm is on cpu zero only
Date: Tue, 8 Nov 2005 14:26:50 +0100 [thread overview]
Message-ID: <20051108132650.GA5850@elte.hu> (raw)
In-Reply-To: <1131458091.25192.29.camel@localhost.localdomain>
* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Maw, 2005-11-08 at 04:53 -0800, Zachary Amsden wrote:
> > Can't hurt, and APM is largely obsolete because of ACPI, so I'm only
> > concerned with trimming and keeping adequate protection of the kernel
> > from APM code while maintaining correctness. I don't have a nice set of
> > old machines with enough wacky APM BIOSen to validate that unpinning the
> > CPU is ok.
>
> A large number of SMP machines, probably the majority of APM based
> ones require that APM calls occur on CPU#0. As I understand it from a
> BIOS engineer involved in debugging that problem Redmond always does
> APM from CPU #0 and may even guarantee it.
ok, then i'm all for making that more explicit - i.e. Zachary's patch is
the right one.
Ingo
next prev parent reply other threads:[~2005-11-08 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 4:33 [PATCH 14/21] i386 Apm is on cpu zero only Zachary Amsden
2005-11-08 7:33 ` Ingo Molnar
2005-11-08 12:53 ` Zachary Amsden
2005-11-08 13:54 ` Alan Cox
2005-11-08 13:26 ` Ingo Molnar [this message]
2005-11-08 14:51 ` H. Peter Anvin
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=20051108132650.GA5850@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chrisl@vmware.com \
--cc=chrisw@osdl.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=pratap@vmware.com \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.com \
--cc=zwane@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.