All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"macro@linux-mips.org" <macro@linux-mips.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: one more apic merging preliminary series
Date: Mon, 18 Aug 2008 13:37:27 -0700	[thread overview]
Message-ID: <20080818203726.GB1152@linux-os.sc.intel.com> (raw)
In-Reply-To: <20080817124540.GF21434@elte.hu>

On Sun, Aug 17, 2008 at 05:45:40AM -0700, Ingo Molnar wrote:
> 
> * Cyrill Gorcunov <gorcunov@gmail.com> wrote:
> 
> > Please review - any comments are welcome!
> >
> > For now it's like code bloating - but it's just preliminary series to
> > make apic_*.c code more or less similar. And it's still a bit far from
> > being ready to be merged down.
> 
> applied to tip/x86/apic - thanks Cyrill.
> 
> Maciej's point about cleaning up the x2apic impact is very much true -
> i've Cc:-ed Suresh and Venki. Even if we wont truly use x2apic in 32-bit
> kernels, it's a piece of glue hardware that does not depend on which
> mode the CPU is in, so support for it should be bitsize agnostic. It
> will also obviously be good for test coverage, once x2apic capable hw
> will be more widespread.

Interrupt-remapping(part of chipset) must be enabled before enabling/using
x2apic mode.

So, there is little bit more work (adding the intr-remapping pieces to 32bit
kernel etc) to be done, before enabling x2apic for 32-bit kernel aswell.

I am planning to do some work (introduce some kind of interrupt-remapping ops
and cleanup some of the code in the existing io_apic_64.c), that will
eventually make it easy to add interrupt-remapping and x2apic to 32bit aswell.

thanks,
suresh

  parent reply	other threads:[~2008-08-18 20:37 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:52     ` Maciej W. Rozycki
2008-08-16 20:00       ` Arjan van de Ven
2008-08-16 20:12         ` Cyrill Gorcunov
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-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-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 [this message]
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=20080818203726.GB1152@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=arjan@infradead.org \
    --cc=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.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 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.