Bug 801727 - qemu-kvm should export max_cpus in FW_CFG_NUMA
Summary: qemu-kvm should export max_cpus in FW_CFG_NUMA
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Eduardo Habkost
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-09 09:42 UTC by Laszlo Ersek
Modified: 2013-01-10 00:45 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-30 16:44:25 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Laszlo Ersek 2012-03-09 09:42:39 UTC
(1) Backport upstream 991dfefd.

(2) Upstream needs a patch for round-robin VCPU distribution over the NUMA nodes:

        if (i == nb_numa_nodes) {
            for (i = 0; i < max_cpus; i++) {
                node_cpumask[i % nb_numa_nodes] |= 1 << i;
            }
        }

- replicate check for max. 64 VCPUs as seen in numa_add()
- make sure LHS of bit-shift is 1ULL (as seen in numa_add().

(BZ reported at upstream state 99c7f878.)

Comment 3 RHEL Program Management 2012-07-10 08:26:55 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 4 RHEL Program Management 2012-07-11 02:03:19 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 7 Laszlo Ersek 2012-10-30 16:44:25 UTC
This bug is fixed as a side-effect of bug 733720. However I'm not marking this as either duplicate or TestOnly: the fix for bug 733720 follows a different design. It actually makes this BZ invalid -- in reality qemu-kvm should *not* export max_cpus in FW_CFG_NUMA, it should do instead what the bug 733720 fix does.


Note You need to log in before you can comment on or make changes to this bug.