All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Li, ZhenHua" <zhen-hual@hp.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel <qemu-devel@nongnu.org>,
	qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH 4/4] Support more than 255 cpus: runtime check
Date: Thu, 15 May 2014 15:16:45 +0800	[thread overview]
Message-ID: <537469DD.7010503@hp.com> (raw)
In-Reply-To: <CAMo8Bf+nF1CXjs2VVomD0u2eNs_P6hRgUxbESHDiDb8ANriyCg@mail.gmail.com>

Maybe it should be 4 bytes for 4096 (0x1000).

On 05/13/2014 04:19 PM, Max Filippov wrote:
> On Tue, May 13, 2014 at 11:09 AM, Li, Zhen-Hua <zhen-hual@hp.com> wrote:
>> From: "Li, ZhenHua" <zhen-hual@hp.com>
>>
>> There is some runtime check for max cpu count. Make them support 4096 cpus.
>>
>> Signed-off-by: Li, ZhenHua <zhen-hual@hp.com>
>> ---
>>   hw/i386/acpi-build.c | 8 ++++----
>>   1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
>> index c98df88..5c3bf10 100644
>> --- a/hw/i386/acpi-build.c
>> +++ b/hw/i386/acpi-build.c
> [...]
>
>> @@ -680,7 +680,7 @@ build_append_notify_method(GArray *device, const char *name,
>>       for (i = 0; i < count; i++) {
>>           GArray *target = build_alloc_array();
>>           build_append_nameseg(target, format, i);
>> -        assert(i < 256); /* Fits in 1 byte */
>> +        assert(i < 4096); /* Fits in 1 byte */
> The comment is no longer true.
> Also the function build_append_notify_method is called with format argument
> set to "CP%0.02X", looks like this should be changed to "CP%0.03X".
>



WARNING: multiple messages have this Message-ID (diff)
From: "Li, ZhenHua" <zhen-hual@hp.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel <qemu-devel@nongnu.org>,
	qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 4/4] Support more than 255 cpus: runtime check
Date: Thu, 15 May 2014 15:16:45 +0800	[thread overview]
Message-ID: <537469DD.7010503@hp.com> (raw)
In-Reply-To: <CAMo8Bf+nF1CXjs2VVomD0u2eNs_P6hRgUxbESHDiDb8ANriyCg@mail.gmail.com>

Maybe it should be 4 bytes for 4096 (0x1000).

On 05/13/2014 04:19 PM, Max Filippov wrote:
> On Tue, May 13, 2014 at 11:09 AM, Li, Zhen-Hua <zhen-hual@hp.com> wrote:
>> From: "Li, ZhenHua" <zhen-hual@hp.com>
>>
>> There is some runtime check for max cpu count. Make them support 4096 cpus.
>>
>> Signed-off-by: Li, ZhenHua <zhen-hual@hp.com>
>> ---
>>   hw/i386/acpi-build.c | 8 ++++----
>>   1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
>> index c98df88..5c3bf10 100644
>> --- a/hw/i386/acpi-build.c
>> +++ b/hw/i386/acpi-build.c
> [...]
>
>> @@ -680,7 +680,7 @@ build_append_notify_method(GArray *device, const char *name,
>>       for (i = 0; i < count; i++) {
>>           GArray *target = build_alloc_array();
>>           build_append_nameseg(target, format, i);
>> -        assert(i < 256); /* Fits in 1 byte */
>> +        assert(i < 4096); /* Fits in 1 byte */
> The comment is no longer true.
> Also the function build_append_notify_method is called with format argument
> set to "CP%0.02X", looks like this should be changed to "CP%0.03X".
>

  reply	other threads:[~2014-05-15  7:18 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     ` Li, ZhenHua [this message]
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

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=537469DD.7010503@hp.com \
    --to=zhen-hual@hp.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=qemu-trivial@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 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.