[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH RFC 4/5] Introduce iothread-group
|
From: |
Fam Zheng |
|
Subject: |
Re: [Qemu-devel] [PATCH RFC 4/5] Introduce iothread-group |
|
Date: |
Wed, 12 Jul 2017 16:44:12 +0800 |
|
User-agent: |
Mutt/1.8.3 (2017-05-23) |
On Tue, 07/11 14:48, Stefan Hajnoczi wrote:
> > + for (i = 0; i < group->size; ++i) {
>
> group->size > INT_MAX must be rejected. The error message below is
> wrong for this property:
>
> if (value < 0) {
> error_setg(&local_err, "%s value must be in range [0, %"PRId64"]",
> info->name, INT64_MAX);
Yes, I can add a PropInfo.max field so "size" can have a different max.
Fam
- [Qemu-devel] [PATCH RFC 0/5] Introduce "-object iothread-group", Fam Zheng, 2017/07/10
- [Qemu-devel] [PATCH RFC 1/5] aio: Wrap poll parameters into AioContextPollParams, Fam Zheng, 2017/07/10
- [Qemu-devel] [PATCH RFC 2/5] iothread: Don't error on windows, Fam Zheng, 2017/07/10
- [Qemu-devel] [PATCH RFC 3/5] iothread: Extract iothread_start, Fam Zheng, 2017/07/10
- [Qemu-devel] [PATCH RFC 4/5] Introduce iothread-group, Fam Zheng, 2017/07/10
- [Qemu-devel] [PATCH RFC 5/5] virtio-blk: Add iothread-group property, Fam Zheng, 2017/07/10
- Re: [Qemu-devel] [PATCH RFC 0/5] Introduce "-object iothread-group", Fam Zheng, 2017/07/10
- Re: [Qemu-devel] [PATCH RFC 0/5] Introduce "-object iothread-group", Stefan Hajnoczi, 2017/07/11
- Re: [Qemu-devel] [PATCH RFC 0/5] Introduce "-object iothread-group", Stefan Hajnoczi, 2017/07/11