From: Zachary Amsden <zach@vmware.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: 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, 08 Nov 2005 04:53:43 -0800 [thread overview]
Message-ID: <43709FD7.1030905@vmware.com> (raw)
In-Reply-To: <20051108073315.GE28201@elte.hu>
Ingo Molnar wrote:
>* Zachary Amsden <zach@vmware.com> wrote:
>
>
>
>>APM BIOS code has a protective wrapper that runs it only on CPU zero.
>>Thus, no need to set APM BIOS segments in the GDT for other CPUs.
>>
>>
>
>hm, do we want (need) to have that CPU#0 assumption forever?
>
>
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.
Zach
next prev parent reply other threads:[~2005-11-08 12:53 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 [this message]
2005-11-08 13:54 ` Alan Cox
2005-11-08 13:26 ` Ingo Molnar
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=43709FD7.1030905@vmware.com \
--to=zach@vmware.com \
--cc=akpm@osdl.org \
--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=mingo@elte.hu \
--cc=pratap@vmware.com \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.org \
--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.