Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932136AbbFDMzf (ORCPT ); Thu, 4 Jun 2015 08:55:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60263 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932068AbbFDMzb (ORCPT ); Thu, 4 Jun 2015 08:55:31 -0400 Date: Thu, 4 Jun 2015 14:55:28 +0200 From: "Michael S. Tsirkin" To: Jiang Liu Cc: Thomas Gleixner , virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] virtio_pci: Clear stale cpumask when setting irq affinity Message-ID: <20150604145513-mutt-send-email-mst@redhat.com> References: <1433407304-22981-1-git-send-email-jiang.liu@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1433407304-22981-1-git-send-email-jiang.liu@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1157 Lines: 33 On Thu, Jun 04, 2015 at 04:41:44PM +0800, Jiang Liu wrote: > The cpumask vp_dev->msix_affinity_masks[info->msix_vector] may contain > staled information when vp_set_vq_affinity() gets called, so clear it > before setting the new cpu bit mask. > > Signed-off-by: Jiang Liu I have queued this up. Thanks! > --- > drivers/virtio/virtio_pci_common.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/virtio/virtio_pci_common.c b/drivers/virtio/virtio_pci_common.c > index e894eb278d83..eba1b7ac7294 100644 > --- a/drivers/virtio/virtio_pci_common.c > +++ b/drivers/virtio/virtio_pci_common.c > @@ -423,6 +423,7 @@ int vp_set_vq_affinity(struct virtqueue *vq, int cpu) > if (cpu == -1) > irq_set_affinity_hint(irq, NULL); > else { > + cpumask_clear(mask); > cpumask_set_cpu(cpu, mask); > irq_set_affinity_hint(irq, mask); > } > -- > 1.7.10.4 -- 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/