From: Giorgio Dal Molin <giorgio.nicole@arcor.de>
To: barebox@lists.infradead.org
Subject: intel efi system too slow
Date: Wed, 18 Oct 2017 12:13:16 +0200 (CEST) [thread overview]
Message-ID: <580704064.144248.1508321596762@mail.vodafone.de> (raw)
Hi,
I'm working on an embedded system with an intel CPU (atom).
I've built a barebox from the current master (v2017.10.0) and it
runs and can actually boot a kernel.
Nevertheless I think the bootloader is very slow, for example when
reading or writing files to the disk (an industrial CFastCard).
After the kernel starts the system becomes fast 'es expected'.
While barebox starts up I noticed the following line on the console:
...
EFI Event timer too slow freq = 50 Hz
...
I found the warning in the source file 'drivers/clocksource/efi.c':
static int efi_cs_init(struct clocksource *cs)
{
efi_status_t efiret;
uint64_t freq;
...
freq = 1000 * 1000;
if (ticks_freq() < 800 * 1000) {
uint64_t nb_100ns;
freq = ticks_freq_x86();
if (freq == 0) {
BS->close_event(efi_cs_evt);
return -ENODEV;
}
nb_100ns = 10 * 1000 * 1000 / freq;
pr_warn("EFI Event timer too slow freq = %llu Hz\n", freq);
efiret = BS->set_timer(efi_cs_evt, EFI_TIMER_PERIODIC, nb_100ns);
if (EFI_ERROR(efiret)) {
BS->close_event(efi_cs_evt);
return -efi_errno(efiret);
}
}
...
}
Can this be a possible reason for a too slow system or is it 'OK'
to see this warning.
I don't really know where I should start searching for a possible
problem or system misconfiguration.
giorgio
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2017-10-18 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 10:13 Giorgio Dal Molin [this message]
2017-10-18 13:06 ` Sascha Hauer
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=580704064.144248.1508321596762@mail.vodafone.de \
--to=giorgio.nicole@arcor.de \
--cc=barebox@lists.infradead.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