Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932184AbbFBN7R (ORCPT ); Tue, 2 Jun 2015 09:59:17 -0400 Received: from www.linutronix.de ([62.245.132.108]:51155 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759019AbbFBN7M (ORCPT ); Tue, 2 Jun 2015 09:59:12 -0400 Date: Tue, 2 Jun 2015 15:59:09 +0200 (CEST) From: Thomas Gleixner To: Feng Wu cc: joro@8bytes.org, dwmw2@infradead.org, jiang.liu@linux.intel.com, iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [v8 3/9] iommu, x86: Implement irq_set_vcpu_affinity for intel_ir_chip In-Reply-To: <1432699544-17444-4-git-send-email-feng.wu@intel.com> Message-ID: References: <1432699544-17444-1-git-send-email-feng.wu@intel.com> <1432699544-17444-4-git-send-email-feng.wu@intel.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1287 Lines: 34 On Wed, 27 May 2015, Feng Wu wrote: > + /* stop posting interrupts, back to remapping mode */ > + if (!vcpu_info) { > + modify_irte(&ir_data->irq_2_iommu, &ir_data->irte_entry); > + } else { > + vcpu_pi_info = (struct vcpu_data *)vcpu_info; > + > + /* > + * "ir_data->irte_entry" saves the remapped format of IRTE, > + * which being a cached irte is still updated when setting > + * the affinity even when we are in posted mode. So this make s/make/makes/ > + * it possible to switch back to remapped mode from posted mode, > + * we can just set "ir_data->irte_entry" to hardware for that > + * purpose. Here we store the posted format of IRTE in another > + * new member "ir_data->irte_pi_entry" to not corrupt Remove the 'another new member' please. That member is not longer new once that patch is applied. Now there is another question. Are we actually using that pi_entry cached value for anything else than this code here? If not, we can do this on the stack and avoid the extra storage in ir_data. Thanks, tglx -- 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/