public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
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>,
	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 06:51:50 -0800	[thread overview]
Message-ID: <4370BB85.9060303@zytor.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?
> 

APM BIOS should only ever run on the BSP, and I believe in Linux the BSP 
is always 0.  Since APM is obsolete, there is no future to consider.

	-hpa

      parent reply	other threads:[~2005-11-08 14:52 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
2005-11-08 14:51   ` H. Peter Anvin [this message]

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=4370BB85.9060303@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@osdl.org \
    --cc=chrisl@vmware.com \
    --cc=chrisw@osdl.org \
    --cc=ebiederm@xmission.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox