linux-kernel - Re: [patch 2/2] x86: arch specific support for remapping HPET MSIs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1249923516.27006.10839.camel@localhost.localdomain>
Date:	Mon, 10 Aug 2009 09:58:36 -0700
From:	Suresh Siddha <suresh.b.siddha@...el.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	"tglx@...utronix.de" <tglx@...utronix.de>,
	"hpa@...or.com" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
	David Woodhouse <dwmw2@...radead.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Jay Fenlason <fenlason@...hat.com>
Subject: Re: [patch 2/2] x86: arch specific support for remapping HPET MSIs

On Sat, 2009-08-08 at 08:12 -0700, Ingo Molnar wrote:
> * Suresh Siddha <suresh.b.siddha@...el.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.

> I like it - but i'll defer to Thomas to queue it up.

thanks,
suresh

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/