From: Stefan Hajnoczi <1441781@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1441781] Re: qemuProcessSetEmulatorAffinity() not behaving as expected
Date: Fri, 10 Apr 2015 10:13:31 -0000 [thread overview]
Message-ID: <20150410101331.26230.51990.launchpad@gac.canonical.com> (raw)
In-Reply-To: 20150408180931.7119.52367.malonedeb@chaenomeles.canonical.com
** Also affects: libvirt
Importance: Undecided
Status: New
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1441781
Title:
qemuProcessSetEmulatorAffinity() not behaving as expected
Status in libvirt virtualization API:
New
Status in QEMU:
Invalid
Bug description:
When running on a 24-CPU host and using vCPU and emulator pinning I've
seen cases where the specified emulator pinning isn't applied as
expected.
It appears the bug was introduced/uncovered by 411cea6 which moved
both qemuSetupCgroupForEmulator() and qemuProcessSetEmulatorAffinity()
up before the call to qemuProcessWaitForMonitor(). Reverting this
commit makes the problem go away.
It's not obvious why this makes a difference, since the pid had to
have been up and running already.
To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/1441781/+subscriptions
prev parent reply other threads:[~2015-04-10 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 18:09 [Qemu-devel] [Bug 1441781] [NEW] qemuProcessSetEmulatorAffinity() called before emulator process actually running Chris Friesen
2015-04-08 18:16 ` [Qemu-devel] [Bug 1441781] " Chris Friesen
2015-04-08 18:26 ` [Qemu-devel] [Bug 1441781] Re: qemuProcessSetEmulatorAffinity() not behaving as expected Chris Friesen
2015-04-10 10:13 ` Stefan Hajnoczi [this message]
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=20150410101331.26230.51990.launchpad@gac.canonical.com \
--to=1441781@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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).