Nico Huber has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/27369 )
Change subject: soc/intel/basecode: Add support for updating ucode loaded via FIT
......................................................................
Patch Set 36:
>>>> Ofc, it's too late for current products. But is there any change
>>>> planned for the FIT update mechanism. e.g. a rule that multiple
>>>> updates for one processor signature are allowed and the newest would
>>>> be applied. That would make this much easier, would allow a single
>>>> RO FIT with some entries pointing to RO and some to the MCU RW and
>>>> we wouldn't need the top-swap feature any more.
>>>>
>>> If you haven't tried, add multiple microcode patches in FIT for the same processor
>>> signature, you will find that FIT will pick the latest revision and load. However
>>> there is no fallback if there is a failure.
>>>
>>
>> Hmm, that's not allowed by the Coffee Lake BWG.
>>
>>> 2 FITs, 1 for normal boot, another for recovery boot.
>>> Even if the CPU manages to load the latest revision (from the
>>> normal boot FIT) and that results in a hang/reboot loop. We need a
>>> tried and tested patch to recover from the hang/reboot for which
>>> the top-swap FIT will be used.
>>
>> That's just relaying the problem of dependable firmware from MCU to
>> coreboot. If things are really that bad that you expect Intel to sign
>> an MCU that results in a boot failure, you shift the problem to this
>> update mechanism here. How can you be sure that no OEM will acciden-
>> tally ship devices with a broken update mechanism in RO? If it's
>> broken, you need a way to recover; a fallback fallback? I understand
>> why you are doing this. I just don't see that it's a good solution.
>
> Nico, Consider the fact that in case of Chrome devices, when we are in "recovery" mode, we need to have absolutely assured way of loading all FW pieces from immutable storage and hence runtime (before cpu reset) selection capability to switch from RO to RW was deemed important and hence the usage of top swap. Other platforms can chose to simply add another uCode entry into FIT and be done with it. I do think that OEMs, when they ship products, will ensure that a bootable uCode is in place which just works. Let me know if you have any other specific concerns.
Thanks for the reasoning, I didn't know about the "recovery"
constraints. I don't have real concerns here, I only tried to
discuss alternatives. And already learned a lot.
Though, I'm still wondering about all the possible and allowed
paths coreboot may take. If I understand you correctly, when
booting to recovery with top-swap set, we'd have to disable it
and reset (to ensure that we run from immutable storage next
time). Wouldn't it result in mostly the same sequence when we'd
use one FIT with multiple entries, erase the RW entries when
booting in recovery and then reset? I'm not proposing to do it
like that, just wondering if it would be feasible.
--
To view, visit https://review.coreboot.org/c/coreboot/+/27369
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: Iab6ba36a2eb587f331fe522c778e2c430c8eb655
Gerrit-Change-Number: 27369
Gerrit-PatchSet: 36
Gerrit-Owner: Rizwan Qureshi <rizwan.qureshi(a)intel.com>
Gerrit-Reviewer: Aaron Durbin <adurbin(a)chromium.org>
Gerrit-Reviewer: Duncan Laurie <dlaurie(a)chromium.org>
Gerrit-Reviewer: Furquan Shaikh <furquan(a)google.com>
Gerrit-Reviewer: Martin Roth <martinroth(a)google.com>
Gerrit-Reviewer: Patrick Georgi <pgeorgi(a)google.com>
Gerrit-Reviewer: Patrick Rudolph <patrick.rudolph(a)9elements.com>
Gerrit-Reviewer: Patrick Rudolph <siro(a)das-labor.org>
Gerrit-Reviewer: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Reviewer: Rizwan Qureshi <rizwan.qureshi(a)intel.com>
Gerrit-Reviewer: Subrata Banik <subrata.banik(a)intel.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Reviewer: dhaval v sharma <dhaval.v.sharma(a)intel.com>
Gerrit-CC: Arthur Heymans <arthur(a)aheymans.xyz>
Gerrit-CC: Dhaval Sharma <dhaval.v.sharma(a)intel.corp-partner.google.com>
Gerrit-CC: Nico Huber <nico.h(a)gmx.de>
Gerrit-Comment-Date: Wed, 16 Jan 2019 11:55:01 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
dhaval v sharma has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/27369 )
Change subject: soc/intel/basecode: Add support for updating ucode loaded via FIT
......................................................................
Patch Set 36:
> Patch Set 35:
>
> >> Ofc, it's too late for current products. But is there any change
> >> planned for the FIT update mechanism. e.g. a rule that multiple
> >> updates for one processor signature are allowed and the newest would
> >> be applied. That would make this much easier, would allow a single
> >> RO FIT with some entries pointing to RO and some to the MCU RW and
> >> we wouldn't need the top-swap feature any more.
> >>
> > If you haven't tried, add multiple microcode patches in FIT for the same processor
> > signature, you will find that FIT will pick the latest revision and load. However
> > there is no fallback if there is a failure.
> >
>
> Hmm, that's not allowed by the Coffee Lake BWG.
>
> > 2 FITs, 1 for normal boot, another for recovery boot.
> > Even if the CPU manages to load the latest revision (from the
> > normal boot FIT) and that results in a hang/reboot loop. We need a
> > tried and tested patch to recover from the hang/reboot for which
> > the top-swap FIT will be used.
>
> That's just relaying the problem of dependable firmware from MCU to
> coreboot. If things are really that bad that you expect Intel to sign
> an MCU that results in a boot failure, you shift the problem to this
> update mechanism here. How can you be sure that no OEM will acciden-
> tally ship devices with a broken update mechanism in RO? If it's
> broken, you need a way to recover; a fallback fallback? I understand
> why you are doing this. I just don't see that it's a good solution.
Nico, Consider the fact that in case of Chrome devices, when we are in "recovery" mode, we need to have absolutely assured way of loading all FW pieces from immutable storage and hence runtime (before cpu reset) selection capability to switch from RO to RW was deemed important and hence the usage of top swap. Other platforms can chose to simply add another uCode entry into FIT and be done with it. I do think that OEMs, when they ship products, will ensure that a bootable uCode is in place which just works. Let me know if you have any other specific concerns.
--
To view, visit https://review.coreboot.org/c/coreboot/+/27369
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: Iab6ba36a2eb587f331fe522c778e2c430c8eb655
Gerrit-Change-Number: 27369
Gerrit-PatchSet: 36
Gerrit-Owner: Rizwan Qureshi <rizwan.qureshi(a)intel.com>
Gerrit-Reviewer: Aaron Durbin <adurbin(a)chromium.org>
Gerrit-Reviewer: Duncan Laurie <dlaurie(a)chromium.org>
Gerrit-Reviewer: Furquan Shaikh <furquan(a)google.com>
Gerrit-Reviewer: Martin Roth <martinroth(a)google.com>
Gerrit-Reviewer: Patrick Georgi <pgeorgi(a)google.com>
Gerrit-Reviewer: Patrick Rudolph <patrick.rudolph(a)9elements.com>
Gerrit-Reviewer: Patrick Rudolph <siro(a)das-labor.org>
Gerrit-Reviewer: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Reviewer: Rizwan Qureshi <rizwan.qureshi(a)intel.com>
Gerrit-Reviewer: Subrata Banik <subrata.banik(a)intel.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Reviewer: dhaval v sharma <dhaval.v.sharma(a)intel.com>
Gerrit-CC: Arthur Heymans <arthur(a)aheymans.xyz>
Gerrit-CC: Dhaval Sharma <dhaval.v.sharma(a)intel.corp-partner.google.com>
Gerrit-CC: Nico Huber <nico.h(a)gmx.de>
Gerrit-Comment-Date: Wed, 16 Jan 2019 11:36:04 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Nico Huber has uploaded this change for review. ( https://review.coreboot.org/c/coreboot/+/30926
Change subject: soc/samsung/exynos5420: Disable BOOTBLOCK_CONSOLE
......................................................................
soc/samsung/exynos5420: Disable BOOTBLOCK_CONSOLE
Add a new Kconfig NO_BOOTBLOCK_CONSOLE to disable the BOOTBLOCK_CONSOLE
option completely. The commit message of fbb11cf (ARM: Separate the
early console (romstage) from the bootblock console.) states that it
doesn't work before romstage on Exynos 5420.
Change-Id: I9b56a52f2555b5233300f27031a9ef50e7ab7cea
Signed-off-by: Nico Huber <nico.h(a)gmx.de>
---
M src/console/Kconfig
M src/soc/samsung/exynos5420/Kconfig
2 files changed, 5 insertions(+), 1 deletion(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/26/30926/1
diff --git a/src/console/Kconfig b/src/console/Kconfig
index 82f7441..61ba667 100644
--- a/src/console/Kconfig
+++ b/src/console/Kconfig
@@ -1,8 +1,11 @@
menu "Console"
+config NO_BOOTBLOCK_CONSOLE
+ bool
+
config BOOTBLOCK_CONSOLE
bool "Enable early (bootblock) console output."
- depends on C_ENVIRONMENT_BOOTBLOCK
+ depends on C_ENVIRONMENT_BOOTBLOCK && !NO_BOOTBLOCK_CONSOLE
default y
help
Use console during the bootblock if supported
diff --git a/src/soc/samsung/exynos5420/Kconfig b/src/soc/samsung/exynos5420/Kconfig
index 7fb2f8f..7b87650 100644
--- a/src/soc/samsung/exynos5420/Kconfig
+++ b/src/soc/samsung/exynos5420/Kconfig
@@ -7,6 +7,7 @@
select GENERIC_UDELAY
select HAVE_UART_SPECIAL
select RELOCATABLE_MODULES
+ select NO_BOOTBLOCK_CONSOLE
bool
default n
--
To view, visit https://review.coreboot.org/c/coreboot/+/30926
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I9b56a52f2555b5233300f27031a9ef50e7ab7cea
Gerrit-Change-Number: 30926
Gerrit-PatchSet: 1
Gerrit-Owner: Nico Huber <nico.h(a)gmx.de>
Gerrit-MessageType: newchange
mikeb mikeb has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/21624 )
Change subject: [WIP] AGESA: Fix SMM support in ASEG
......................................................................
Patch Set 4:
> Patch Set 4:
> It moves the SMI handle enablement from mainboard to chipset.
Please tell, what is the primary practical benefit of this move?
> It was previously tested on asus/f2a85-m and asrock/imb-a180, but not after rebasing. Plan is to see if I should refactor code more and include fam14 here as well.
I could test it on G505S, is it ready for this test at the moment?
--
To view, visit https://review.coreboot.org/c/coreboot/+/21624
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I7a6b63c535b51cc6ff6847b78616134c8506ad28
Gerrit-Change-Number: 21624
Gerrit-PatchSet: 4
Gerrit-Owner: Kyösti Mälkki <kyosti.malkki(a)gmail.com>
Gerrit-Reviewer: Alexander Couzens <lynxis(a)fe80.eu>
Gerrit-Reviewer: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-Reviewer: Kyösti Mälkki <kyosti.malkki(a)gmail.com>
Gerrit-Reviewer: Martin Roth <martinroth(a)google.com>
Gerrit-Reviewer: Patrick Georgi <pgeorgi(a)google.com>
Gerrit-Reviewer: Patrick Rudolph <siro(a)das-labor.org>
Gerrit-Reviewer: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: mikeb mikeb <mikebdp2(a)gmail.com>
Gerrit-Comment-Date: Wed, 16 Jan 2019 10:34:53 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
mikeb mikeb has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/21624 )
Change subject: [WIP] AGESA: Fix SMM support in ASEG
......................................................................
Patch Set 4:
> Patch Set 4:
> It moves the SMI handle enablement from mainboard to chipset.
Please tell, what is the primary practical benefit of this move?
> It was previously tested on asus/f2a85-m and asrock/imb-a180, but not after rebasing. Plan is to see if I should refactor code more and include fam14 here as well.
I could test it on G505S, is it ready for this test at the moment?
--
To view, visit https://review.coreboot.org/c/coreboot/+/21624
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I7a6b63c535b51cc6ff6847b78616134c8506ad28
Gerrit-Change-Number: 21624
Gerrit-PatchSet: 4
Gerrit-Owner: Kyösti Mälkki <kyosti.malkki(a)gmail.com>
Gerrit-Reviewer: Alexander Couzens <lynxis(a)fe80.eu>
Gerrit-Reviewer: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-Reviewer: Kyösti Mälkki <kyosti.malkki(a)gmail.com>
Gerrit-Reviewer: Martin Roth <martinroth(a)google.com>
Gerrit-Reviewer: Patrick Georgi <pgeorgi(a)google.com>
Gerrit-Reviewer: Patrick Rudolph <siro(a)das-labor.org>
Gerrit-Reviewer: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: mikeb mikeb <mikebdp2(a)gmail.com>
Gerrit-Comment-Date: Wed, 16 Jan 2019 10:33:15 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Kyösti Mälkki has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/21624 )
Change subject: [WIP] AGESA: Fix SMM support in ASEG
......................................................................
Patch Set 4:
> Patch Set 4:
>
> I've been CC'd regarding this CB:21624 change but it's marked as [WIP]. Is it ready for testing on real hardware?
It moves the SMI handle enablement from mainboard to chipset. It was previously tested on asus/f2a85-m and asrock/imb-a180, but not after rebasing. Plan is to see if I should refactor code more and include fam14 here as well.
--
To view, visit https://review.coreboot.org/c/coreboot/+/21624
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I7a6b63c535b51cc6ff6847b78616134c8506ad28
Gerrit-Change-Number: 21624
Gerrit-PatchSet: 4
Gerrit-Owner: Kyösti Mälkki <kyosti.malkki(a)gmail.com>
Gerrit-Reviewer: Alexander Couzens <lynxis(a)fe80.eu>
Gerrit-Reviewer: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-Reviewer: Kyösti Mälkki <kyosti.malkki(a)gmail.com>
Gerrit-Reviewer: Martin Roth <martinroth(a)google.com>
Gerrit-Reviewer: Patrick Georgi <pgeorgi(a)google.com>
Gerrit-Reviewer: Patrick Rudolph <siro(a)das-labor.org>
Gerrit-Reviewer: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: mikeb mikeb <mikebdp2(a)gmail.com>
Gerrit-Comment-Date: Wed, 16 Jan 2019 10:16:58 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
HAOUAS Elyes has uploaded a new patch set (#2) to the change originally created by Patrick Rudolph. ( https://review.coreboot.org/c/coreboot/+/30502 )
Change subject: cpu/x86/mtrr: Fix sign overflow
......................................................................
cpu/x86/mtrr: Fix sign overflow
Use unsigned long to prevent sign overflow.
Fixes wrong MTRRs settings on x86_64 romstage.
Signed-off-by: Patrick Rudolph <siro(a)das-labor.org>
Change-Id: I71b61a45becc17bf60a619e4131864c82a16b0d1
---
M src/include/cpu/x86/mtrr.h
1 file changed, 1 insertion(+), 1 deletion(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/02/30502/2
--
To view, visit https://review.coreboot.org/c/coreboot/+/30502
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I71b61a45becc17bf60a619e4131864c82a16b0d1
Gerrit-Change-Number: 30502
Gerrit-PatchSet: 2
Gerrit-Owner: Patrick Rudolph <siro(a)das-labor.org>
Gerrit-Reviewer: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-Reviewer: Arthur Heymans <arthur(a)aheymans.xyz>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-MessageType: newpatchset
HAOUAS Elyes has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/25600 )
Change subject: nb/intel/i945: Use parallel MP init
......................................................................
Patch Set 38: Code-Review+1
--
To view, visit https://review.coreboot.org/c/coreboot/+/25600
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I955551b99e9cbc397f99c2a6bd355c6070390bcb
Gerrit-Change-Number: 25600
Gerrit-PatchSet: 38
Gerrit-Owner: Arthur Heymans <arthur(a)aheymans.xyz>
Gerrit-Reviewer: Arthur Heymans <arthur(a)aheymans.xyz>
Gerrit-Reviewer: HAOUAS Elyes <ehaouas(a)noos.fr>
Gerrit-Reviewer: Martin Roth <martinroth(a)google.com>
Gerrit-Reviewer: Patrick Georgi <pgeorgi(a)google.com>
Gerrit-Reviewer: Patrick Rudolph <siro(a)das-labor.org>
Gerrit-Reviewer: Paul Menzel <paulepanter(a)users.sourceforge.net>
Gerrit-Reviewer: Stefan Reinauer <stefan.reinauer(a)coreboot.org>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-Comment-Date: Wed, 16 Jan 2019 09:48:41 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment