From: Jack Steiner <steiner@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>,
Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: [PATCH] - UV fix for size of hub mappings
Date: Sat, 27 Sep 2008 14:56:16 -0500 [thread overview]
Message-ID: <20080927195615.GA244243@sgi.com> (raw)
In-Reply-To: <20080927174233.GB26047@elte.hu>
On Sat, Sep 27, 2008 at 07:42:33PM +0200, Ingo Molnar wrote:
>
> * Jack Steiner <steiner@sgi.com> wrote:
>
> > Fix the size of the mappings of UV hub registers. Size must be a
> > function of the maximum node number within the SSI.
> >
> > Signed-off-by: Jack Steiner <steiner@sgi.com>
>
> applied to tip/x86/uv, thanks Jack!
>
> i'm wondering, the code still has a couple of ZZZ fixmes like:
>
> #ifdef ZZZ /* Needs x2apic patch */
> static void uv_send_IPI_self(int vector)
> {
> apic_write(APIC_SELF_IPI, vector);
> }
> #endif
>
> x2apic support is available in tip/master, so it would be nice to glue
> UV to generic x2apic support properly and remove duplication and fixmes.
Good point. I'll send the fixes to you early next week. Recently,
I've been focused on a distro release which is still waiting for
the x2apic code. However, I don't need to wait to fix this upstream...
> For example, do we really need apic_x2apic_uv_x, or could we use
> apic_x2apic_cluster?
Unfortunately, we really need a uv genapic. IPIs on large UV systems
can't use an x2apic model. Because of the size of our large systems, APICIDs
in the cpu MSRs are not globally unique. We have a special feature
in the UV chipset that must be used for on large systems for IPIs.
Small & medium sized system can and do use the x2apic genapic.
--- jack
next prev parent reply other threads:[~2008-09-27 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 12:52 Jack Steiner
2008-09-27 17:42 ` Ingo Molnar
2008-09-27 19:56 ` Jack Steiner [this message]
2008-09-27 20:02 ` 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=20080927195615.GA244243@sgi.com \
--to=steiner@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/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
all inboxes | Powered by JetHome®