To simplify the process of building release versions in a directory
under git, we will give priority to the file .version and
not the version in git.
Signed-off-by: Alexey Kirillov
---
scripts/buildversion.py | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git
manually and will not affect existing builds.
Alexey Kirillov (1):
build: increase .version priority over git
scripts/buildversion.py | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
--
2.17.1
___
SeaBIOS mailing list
Hi,
14.01.2020, 12:25, "Gerd Hoffmann" :
> Check NVMe devices whenever they are bootable,
> skip initialization in case they are not.
>
> Signed-off-by: Gerd Hoffmann
Reviewed-by: Alexey Kirillov
> ---
> src/hw/nvme.c | 7 +++
> 1 file changed, 7 insert
Hi,
14.01.2020, 12:25, "Gerd Hoffmann" :
> Check each disk attached to a virtio-scsi device whenever
> it is bootable and skip initialization in case it isn't.
>
> Signed-off-by: Gerd Hoffmann
Reviewed-by: Alexey Kirillov
> ---
> src/hw/virtio-scsi.c | 11
Hi,
14.01.2020, 12:25, "Gerd Hoffmann" :
> Call find_prio("HALT") only once, on first is_bootprio_strict() call.
> Store the result in a variable and reuse it on subsequent calls.
>
> Signed-off-by: Gerd Hoffmann
Reviewed-by: Alexey Kirillov
> ---
> src/
10 devices,
we can't boot from any of the following (11, 12, etc.).
We can initialize only bootable devices, i.e. listed in boot order list,
that this patch does.
Alexey Kirillov (2):
boot: Detect strict boot order (HALT record) in function
virtio: Do not init non-bootable devices
src/b
Introduce is_bootprio_strict().
We will reuse this function in the next commit.
Signed-off-by: Alexey Kirillov
---
src/boot.c | 5 +
src/util.h | 1 +
2 files changed, 6 insertions(+)
diff --git a/src/boot.c b/src/boot.c
index ea18194..5182ab4 100644
--- a/src/boot.c
+++ b/src/boot.c
Because initializing a virtio-blk or virtio-scsi device requires a large
amount of memory, you cannot create more than about 10 virtio devices.
Since initialization is required for booting from media, we will not
initialize those devices that are not in the boot order list.
Signed-off-by: Alexey
Because initializing a virtio-blk or virtio-scsi device requires a large
amount of memory, you cannot create more than about 10 virtio devices.
Since initialization is required for booting from media, we will not
initialize those devices that are not in the boot order list.
Signed-off-by: Alexey
Introduce is_bootprio_strict().
We will reuse this function in the next commit.
Signed-off-by: Alexey Kirillov
---
src/boot.c | 5 +
src/util.h | 1 +
2 files changed, 6 insertions(+)
diff --git a/src/boot.c b/src/boot.c
index ea18194..e9b2cd0 100644
--- a/src/boot.c
+++ b/src/boot.c
10 devices,
we can't boot from any of the following (11, 12, etc.).
We can initialize only bootable devices, i.e. listed in boot order list,
that this patch does.
Alexey Kirillov (2):
boot: Detect strict boot order (HALT record) in function
virtio: Do not init non-bootable devices
src/b
ot be able to boot from any and all
devices that are not in the boot order. But we wanted only to avoid
initializing virtio-blk/scsi specifically (at least for now).
What do you think?
--
Alexey Kirillov
Yandex.Cloud
___
SeaBIOS mailing list -- se
Because initializing a virtio-blk or virtio-scsi device requires a large
amount of memory, you cannot create more than about 10 virtio devices.
Since initialization is required for booting from media, we will not
initialize those devices that are not in the boot order list.
Signed-off-by: Alexey
10 devices,
we can't boot from any of the following (11, 12, etc.).
We can initialize only bootable devices, i.e. listed in boot order list,
that this patch does.
Alexey Kirillov (1):
virtio: do not init non-bootable devices
docs/Runtime_config.md | 1 +
src/hw/virtio-blk.c
14 matches
Mail list logo
