All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Li, ZhenHua" <zhen-hual@hp.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
	qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] Support more than 255 cpus
Date: Thu, 15 May 2014 10:35:00 +0200	[thread overview]
Message-ID: <53747C34.1060602@siemens.com> (raw)
In-Reply-To: <537469B3.4030807@hp.com>

On 2014-05-15 09:16, Li, ZhenHua wrote:
> Kernel's kvm support is not here.
> x2APIC is needed, I will try to do that later.

x2APIC emulation can wait if KVM support is there. But we need at least
one of them before starting to think about raising the limit.

Jan

PS: Please don't top-post.

> 
> On 05/13/2014 06:53 PM, Jan Kiszka wrote:
>> On 2014-05-13 09:09, Li, Zhen-Hua wrote:
>>> From: "Li, ZhenHua" <zhen-hual@hp.com>
>>>
>>> These series patches are trying to make Qemu support more than 255 CPUs.
>>> The max cpu number changed to 4096.
>>>
>>>   Support more than 255 cpus: ACPI and APIC defines
>>>   Support more than 255 cpus: max_cpus to 4096
>>>   Support more than 255 cpus: max cpumask bit to 4096
>>>   Support more than 255 cpus: runtime chec
>>>
>>>   include/hw/acpi/cpu_hotplug_defs.h | 4 ++--
>>>   include/hw/i386/apic_internal.h    | 2 +-
>>>   include/hw/i386/pc.h | 2 +-
>>>   include/sysemu/sysemu.h | 2 +-
>>>   hw/i386/acpi-build.c | 8 ++++----
>> Don't we need x2APIC support to provide >255 CPUs? Where so you enforce
>> this, i.e. keep the restriction to 255 CPUs when we are not in KVM mode
>> with in-kernel APIC (the emulate APIC lacks x2APIC mode, unfortunately)?
>> But, wait, KVM only supports up to 255 VCPUs. So what are you
>> targeting at?
>>
>> Jan
>>
> 

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux

      reply	other threads:[~2014-05-15  8:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13  7:09 [Qemu-trivial] [PATCH 0/4] Support more than 255 cpus Li, Zhen-Hua
2014-05-13  7:09 ` [Qemu-devel] " Li, Zhen-Hua
2014-05-13  7:09 ` [Qemu-trivial] [PATCH 1/4] Support more than 255 cpus: ACPI and APIC defines Li, Zhen-Hua
2014-05-13  7:09   ` [Qemu-devel] " Li, Zhen-Hua
2014-05-13  7:09 ` [Qemu-trivial] [PATCH 2/4] Support more than 255 cpus: max_cpus to 4096 Li, Zhen-Hua
2014-05-13  7:09   ` [Qemu-devel] " Li, Zhen-Hua
2014-05-13  7:09 ` [Qemu-trivial] [PATCH 3/4] Support more than 255 cpus: max cpumask bit " Li, Zhen-Hua
2014-05-13  7:09   ` [Qemu-devel] " Li, Zhen-Hua
2014-05-13  7:09 ` [Qemu-trivial] [PATCH 4/4] Support more than 255 cpus: runtime check Li, Zhen-Hua
2014-05-13  7:09   ` [Qemu-devel] " Li, Zhen-Hua
2014-05-13  8:19   ` [Qemu-trivial] " Max Filippov
2014-05-13  8:19     ` Max Filippov
2014-05-15  7:16     ` [Qemu-trivial] " Li, ZhenHua
2014-05-15  7:16       ` Li, ZhenHua
2014-05-15 12:36       ` [Qemu-trivial] " Max Filippov
2014-05-15 12:36         ` Max Filippov
2014-05-13  9:12 ` [Qemu-trivial] [Qemu-devel] [PATCH 0/4] Support more than 255 cpus Andreas Färber
2014-05-13  9:12   ` Andreas Färber
2014-05-13 10:53 ` Jan Kiszka
2014-05-15  7:16   ` Li, ZhenHua
2014-05-15  8:35     ` Jan Kiszka [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=53747C34.1060602@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhen-hual@hp.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.