kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.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)	[thread overview]
Message-ID: <20121127181308.14D5B11FB3B@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-50891-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=50891





--- Comment #3 from Alex Williamson <alex.williamson@redhat.com>  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.

  parent reply	other threads:[~2012-11-27 18:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 15:37 [Bug 50891] New: The smp_affinity cannot work correctly when PCI passthrough device using msi/msi-x with KVM bugzilla-daemon
2012-11-22 17:37 ` [Bug 50891] The smp_affinity cannot work correctly on guest os " bugzilla-daemon
2012-11-26 19:32 ` bugzilla-daemon
2012-11-27  0:57 ` bugzilla-daemon
2012-11-27 18:13 ` bugzilla-daemon [this message]
2012-11-29 15:38 ` bugzilla-daemon
2012-11-29 16:10 ` bugzilla-daemon
2012-11-29 16:21 ` bugzilla-daemon
2012-11-29 16:33 ` bugzilla-daemon
2012-11-29 17:52 ` bugzilla-daemon
2012-11-29 18:08 ` bugzilla-daemon
2012-11-29 18:18 ` bugzilla-daemon
2012-11-29 18:21 ` bugzilla-daemon
2012-11-29 18:55 ` bugzilla-daemon
2012-11-29 19:12 ` bugzilla-daemon
2012-12-03 13:18 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121127181308.14D5B11FB3B@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).