From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: ARM*-EFI timers
Date: Thu, 7 Jan 2016 20:55:02 +0100 [thread overview]
Message-ID: <568EC296.9080606@gmail.com> (raw)
In-Reply-To: <568EB5A8.7080704@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On 07.01.2016 19:59, Andrei Borzenkov wrote:
> 07.01.2016 21:08, Vladimir 'φ-coder/phcoder' Serbinenko пишет:
>> Hello, all. In my automated tests I found out that on ARM64-EFI sleep 10
>> actually sleeps for 100s. The culprit is that EFI doesn't call our timer
>> every 1ms but every 10ms. I propose time1.diff to correct: request EFI
>> to call us every 10ms and increment timer variable by 10.
>
> openSUSE carries similar patch for quite some time. Patch is authored by
> RH. So it can be considered tested in real life.
>
> https://build.opensuse.org/package/view_file/Base:System/grub2/grub2-arm64-Reduce-timer-event-frequency-by-10.patch?expand=1
>
Ok, I took RH patch. Now question is about the second patch
>> For arm64 I propose to use CPU timer instead time2.diff. Can any of ARM
>> guys comment on this?
>>
>>
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>
>
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
prev parent reply other threads:[~2016-01-07 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 18:08 ARM*-EFI timers Vladimir 'φ-coder/phcoder' Serbinenko
2016-01-07 18:59 ` Andrei Borzenkov
2016-01-07 19:55 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=568EC296.9080606@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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).