diff options
| author | Thomas Huth <thuth@redhat.com> | 2016-08-31 05:00:14 +0200 |
|---|---|---|
| committer | Alexey Kardashevskiy <aik@ozlabs.ru> | 2016-09-14 16:55:36 +1000 |
| commit | b3fde41bc75269df2e30a7dfc0645ca239eb2786 (patch) | |
| tree | a04cff3f92a6ff3d3afdf55642b603026aa2d4d9 /slof/allocator.c | |
| parent | fb9d0b43cffe806a7fc9a068f79d0e5552efdd39 (diff) | |
| download | SLOF-b3fde41bc75269df2e30a7dfc0645ca239eb2786.zip SLOF-b3fde41bc75269df2e30a7dfc0645ca239eb2786.tar.gz SLOF-b3fde41bc75269df2e30a7dfc0645ca239eb2786.tar.bz2 | |
Do not include the FCode evaluator by default anymore
Commit 2fed5652819ad26627a8 ("Always include evaluator, move
framebuffer token init to fbuffer.fs") made sure that the FCode
evaluator is always included, during each boot cycle. The basic
idea was that we would soon be starting to support PCI cards with
FCode drivers on them. However, this has never happened, and so
this change was in vain. The bad thing is now that the inclusion
of the FCode evaluator also takes a lot of precious boot time,
e.g. when running in QEMU TCG mode, it is more than a second.
So to be able to boot faster again, disable the FCode evaluator
by default again and put it into the ROM-fs instead (so it still
can be loaded manually with "include evaluator.fs" if necessary).
Signed-off-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Diffstat (limited to 'slof/allocator.c')
0 files changed, 0 insertions, 0 deletions