From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 50891] The smp_affinity cannot work correctly on guest os when
PCI passthrough device using msi/msi-x with KVM
Date: Tue, 27 Nov 2012 18:13:08 +0000 (UTC)
Message-ID: <20121127181308.14D5B11FB3B@bugzilla.kernel.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
To: kvm@vger.kernel.org
Return-path:
Received: from mail.kernel.org ([198.145.19.201]:40529 "EHLO mail.kernel.org"
rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
id S1755961Ab2K0SNN (ORCPT );
Tue, 27 Nov 2012 13:13:13 -0500
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id 1867220326
for ; Tue, 27 Nov 2012 18:13:12 +0000 (UTC)
Received: from bugzilla.kernel.org (bugzilla.kernel.org [198.145.19.217])
by mail.kernel.org (Postfix) with ESMTP id 7898520337
for ; Tue, 27 Nov 2012 18:13:10 +0000 (UTC)
In-Reply-To:
Sender: kvm-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=50891
--- Comment #3 from Alex Williamson 2012-11-27 18:13:07 ---
I tested a BCM5716 on 3.7.0-rc7 with both qemu-kvm-1.2.0 and current qemu.git
using pci-assign. MSI-X pinning works exactly as expected. Note that Linux
MSI affinity is setup lazily on the next interrupt for a vector, so it's normal
that after setting the affinity for a vector that you might see a single
interrupt on another CPU before the interrupt is moved. Also note that setting
the affinity in the guest only changes the affinity of the virtual interrupt to
the guest, the physical interrupt affinity must be separately configured on the
host. Perhaps the steps your missing in comment 0 above is to disable
irqbalance in the host and set the irq affinity of the kvm interrupts in the
host.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are watching the assignee of the bug.