From: Paolo Bonzini <pbonzini@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>,
P J P <ppandit@redhat.com>,
Qemu Developers <qemu-devel@nongnu.org>
Cc: "Huawei PSIRT" <PSIRT@huawei.com>,
"Prasad J Pandit" <pjp@fedoraproject.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] dma: rc4030: limit interval timer reload value
Date: Thu, 10 Nov 2016 15:50:07 +0100 [thread overview]
Message-ID: <9d8d6a84-1220-2e61-dbdc-b86d5e348bef@redhat.com> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020B0429759@SZXEMA503-MBS.china.huawei.com>
On 10/11/2016 06:56, Gonglei (Arei) wrote:
> Any ideas about this fix?
It seems sensible, but perhaps the field is even smaller. Let's CC
Hervé and Aurelien as I don't have a datasheet for this device.
Also, s->itr is used here:
tm_hz = 1000 / (s->itr + 1);
timer_mod(s->periodic_timer, qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL) +
NANOSECONDS_PER_SECOND / tm_hz);
and this is the same as
timer_mod(s->periodic_timer, qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL) +
NANOSECONDS_PER_SECOND / 1000 * (s->itr + 1));
so perhaps it's better to do it like that.
Paolo
>> -----Original Message-----
>> From: Qemu-devel
>> [mailto:qemu-devel-bounces+arei.gonglei=huawei.com@nongnu.org] On
>> Behalf Of P J P
>> Sent: Wednesday, October 12, 2016 8:38 PM
>> To: Qemu Developers
>> Cc: Paolo Bonzini; Huawei PSIRT; Prasad J Pandit; Michael S. Tsirkin
>> Subject: [Qemu-devel] [PATCH] dma: rc4030: limit interval timer reload value
>>
>> From: Prasad J Pandit <pjp@fedoraproject.org>
>>
>> The JAZZ RC4030 chipset emulator has a periodic timer and
>> associated interval reload register. The reload value is used
>> as divider when computing timer's next tick value. If reload
>> value is large, it could lead to divide by zero error. Limit
>> the interval reload value to avoid it.
>>
>> Reported-by: Huawei PSIRT <psirt@huawei.com>
>> Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
>> ---
>> hw/dma/rc4030.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/hw/dma/rc4030.c b/hw/dma/rc4030.c
>> index 2f2576f..c1b4997 100644
>> --- a/hw/dma/rc4030.c
>> +++ b/hw/dma/rc4030.c
>> @@ -460,7 +460,7 @@ static void rc4030_write(void *opaque, hwaddr addr,
>> uint64_t data,
>> break;
>> /* Interval timer reload */
>> case 0x0228:
>> - s->itr = val;
>> + s->itr = val & 0x01FF;
>> qemu_irq_lower(s->timer_irq);
>> set_next_tick(s);
>> break;
>> --
>> 2.5.5
>>
>
>
>
next prev parent reply other threads:[~2016-11-10 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 12:37 [Qemu-devel] [PATCH] dma: rc4030: limit interval timer reload value P J P
2016-11-10 5:56 ` Gonglei (Arei)
2016-11-10 14:50 ` Paolo Bonzini [this message]
2016-11-16 5:50 ` Hervé Poussineau
2016-11-16 6:03 ` Gonglei (Arei)
2016-11-16 6:29 ` P J P
2016-11-16 6:37 ` Hervé Poussineau
2016-11-17 11:48 ` Paolo Bonzini
2017-03-14 19:17 ` Cole Robinson
2017-03-14 19:35 ` Peter Maydell
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=9d8d6a84-1220-2e61-dbdc-b86d5e348bef@redhat.com \
--to=pbonzini@redhat.com \
--cc=PSIRT@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=aurelien@aurel32.net \
--cc=hpoussin@reactos.org \
--cc=mst@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.com \
--cc=qemu-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).