Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753741Ab2EVHed (ORCPT ); Tue, 22 May 2012 03:34:33 -0400 Received: from mail-bk0-f46.google.com ([209.85.214.46]:53224 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753157Ab2EVHec (ORCPT ); Tue, 22 May 2012 03:34:32 -0400 Date: Tue, 22 May 2012 11:34:27 +0400 From: Cyrill Gorcunov To: Ingo Molnar Cc: Suresh Siddha , agordeev@redhat.com, yinghai@kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org Subject: Re: [PATCH 2/2] x2apic, cluster: use all the members of one cluster specified in the smp_affinity mask for the interrupt desintation Message-ID: <20120522073427.GA1442@moon> References: <1337643880.1997.166.camel@sbsiddha-desk.sc.intel.com> <1337644682-19854-1-git-send-email-suresh.b.siddha@intel.com> <1337644682-19854-2-git-send-email-suresh.b.siddha@intel.com> <20120522070428.GA15738@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120522070428.GA15738@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 911 Lines: 22 On Tue, May 22, 2012 at 09:04:29AM +0200, Ingo Molnar wrote: > > * Suresh Siddha wrote: > > > If the HW implements round-robin interrupt delivery, this > > enables multiple cpu's (which are part of the user specified > > interrupt smp_affinity mask and belong to the same x2apic > > cluster) to service the interrupt. > > Could/should we do something similar for regular APICs as well? > They too support masks and LowestPrio delivery - and doing that > will increase test coverage rather significantly. It seems only es7000_cpu_mask_to_apicid could be tuned up to produce per-cluster mask instead of yielding bad-apic? Cyrill -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/