From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
mingo@elte.hu, hpa@zytor.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] x86: apic - unify lapic_resume
Date: Sun, 17 Aug 2008 00:12:35 +0400 [thread overview]
Message-ID: <20080816201235.GB7182@lenovo> (raw)
In-Reply-To: <20080816130008.349b031d@infradead.org>
[Arjan van de Ven - Sat, Aug 16, 2008 at 01:00:08PM -0700]
| On Sat, 16 Aug 2008 20:52:07 +0100 (BST)
| "Maciej W. Rozycki" <macro@linux-mips.org> wrote:
|
| > On Sat, 16 Aug 2008, Cyrill Gorcunov wrote:
| >
| > > +#ifdef CONFIG_X86_64
| > > + if (x2apic)
| > > + enable_x2apic();
| > > + else
| > > +#endif
| >
| > Hmm, x86-64 hardware can run a 32-bit kernel, so it might be a good
| > idea to take the opportunity of the merge and extend x2APIC support
| > to the 32-bit configuration too. It should be mostly a mechanical
| > change. Just a suggestion though -- feel free to ignore if you'd
| > rather not dive into it. ;)
|
| it's not like you can/want to go over 128 cpus on a 32 bit kernel
| though..
| --
| If you want to reach me at my work email, use arjan@linux.intel.com
| For development, discussion and tips for power savings,
| visit http://www.lesswatts.org
|
Arjan,
it seems this limit is not APIC related since iirc 82489DX allows
to address 2^14 bits, x2APIC - more then 128 entities too. So I suspect
it somehow cpu bitmap related. Am I wrong (I didn't _check_ the code)?
- Cyrill -
next prev parent reply other threads:[~2008-08-16 20:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-16 19:21 one more apic merging preliminary series Cyrill Gorcunov
2008-08-16 19:21 ` [PATCH 1/6] x86: apic - unify clear_local_APIC Cyrill Gorcunov
2008-08-16 19:21 ` [PATCH 2/6] x86: apic - unify lapic_resume Cyrill Gorcunov
2008-08-16 19:21 ` [PATCH 3/6] x86: apic - unify lapic_suspend Cyrill Gorcunov
2008-08-16 19:21 ` [PATCH 4/6] x86: apic - rearrange functions and comments Cyrill Gorcunov
2008-08-16 19:21 ` [PATCH 5/6] x86: apic - unify lapic_is_integrated Cyrill Gorcunov
2008-08-16 19:21 ` [PATCH 6/6] x86: apic - unify xapic_icr_read Cyrill Gorcunov
2008-08-16 19:52 ` [PATCH 2/6] x86: apic - unify lapic_resume Maciej W. Rozycki
2008-08-16 20:00 ` Arjan van de Ven
2008-08-16 20:12 ` Cyrill Gorcunov [this message]
2008-08-18 14:19 ` Maciej W. Rozycki
2008-08-18 14:39 ` Cyrill Gorcunov
2008-08-16 20:25 ` Maciej W. Rozycki
2008-08-16 20:05 ` Cyrill Gorcunov
2008-08-17 12:45 ` one more apic merging preliminary series Ingo Molnar
2008-08-17 13:12 ` Cyrill Gorcunov
2008-08-18 20:37 ` Suresh Siddha
2008-08-19 0:21 ` Ingo Molnar
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=20080816201235.GB7182@lenovo \
--to=gorcunov@gmail.com \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).