From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39171) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPzhq-0000ki-9P for qemu-devel@nongnu.org; Tue, 18 Mar 2014 15:29:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WPzhi-0003kM-Kx for qemu-devel@nongnu.org; Tue, 18 Mar 2014 15:29:46 -0400 Received: from mx1.redhat.com ([209.132.183.28]:14066) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPzhi-0003jB-CS for qemu-devel@nongnu.org; Tue, 18 Mar 2014 15:29:38 -0400 From: Eduardo Habkost Date: Tue, 18 Mar 2014 16:29:22 -0300 Message-Id: <1395170964-32589-1-git-send-email-ehabkost@redhat.com> Subject: [Qemu-devel] [PATCH 0/2] Document MAX_CPUMASK_BITS and use it when limiting max_cpus List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: "Michael S. Tsirkin" , Hu Tao , Igor Mammedov , Laszlo Ersek , =?UTF-8?q?Andreas=20F=C3=A4rber?= , Wanlong Gao Small rework of patches 6/7 and 7/7 from the previous APIC-ID-limit series I sent (which broke the build and where reverted). Instead of renaming MAX_CPUMASK_BITS like I did previously, just document it and use it on the (max_cpus > 255) check on vl.c. Eduardo Habkost (2): sysemu.h: Document what MAX_CPUMASK_BITS really limits vl.c: Use MAX_CPUMASK_BITS macro instead of hardcoded constant include/sysemu/sysemu.h | 7 +++++++ vl.c | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) -- 1.8.5.3