public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Jay Fenlason <fenlason@redhat.com>
Subject: Re: [patch 2/2] x86: arch specific support for remapping HPET MSIs
Date: Mon, 10 Aug 2009 20:51:56 +0200	[thread overview]
Message-ID: <20090810185156.GC9601@elte.hu> (raw)
In-Reply-To: <1249923516.27006.10839.camel@localhost.localdomain>


* Suresh Siddha <suresh.b.siddha@intel.com> wrote:

> On Sat, 2009-08-08 at 08:12 -0700, Ingo Molnar wrote:
> > * Suresh Siddha <suresh.b.siddha@intel.com> wrote:
> > 
> > > x86 arch support for remapping HPET MSI's by associating the HPET 
> > > timer block with the interrupt-remapping HW unit and setting up 
> > > appropriate irq_chip
> > 
> > interesting. This means we'd materially utilize the irq-remapper 
> > not just on relatively obscure, virtualization related setups, 
> > but also in the native x86 bootup mode, on all (hpet+remap 
> > capable) Linux systems?
> 
> Ingo, For native linux kernel, interrupt-remapping allows simple 
> and reliable irq migration from the process context (in addition 
> to its need for supporting cpu's capable of x2apic). And as such 
> solves the issues we had in the past with cpu hotplug and irq 
> migration.

It's something much more directly useful than a fix for race 
conditions, and it would be used in a broader range of hardware
than x2apic. (Not to denounce its other uses - i was just upbeat 
about it getting even more mainstream use.)

	Ingo

  reply	other threads:[~2009-08-10 18:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04 19:07 [patch 1/2] intr-remap: generic support for remapping HPET MSIs Suresh Siddha
2009-08-04 19:07 ` [patch 2/2] x86: arch specific " Suresh Siddha
2009-08-08 15:12   ` Ingo Molnar
2009-08-10 16:58     ` Suresh Siddha
2009-08-10 18:51       ` Ingo Molnar [this message]
2009-08-10 16:58     ` Jesse Barnes
2009-08-27 21:37   ` [tip:timers/hpet] " tip-bot for Suresh Siddha
2009-08-27 21:37 ` [tip:timers/hpet] intr-remap: generic " tip-bot for Suresh Siddha

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=20090810185156.GC9601@elte.hu \
    --to=mingo@elte.hu \
    --cc=dwmw2@infradead.org \
    --cc=fenlason@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suresh.b.siddha@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox