Reminder: Unix platform working group meeting (02/05 8AM PST) @ Wed Feb 5, 2020 8am - 9am (PST) When: Wednesday, 5 February 2020, 8:00am to 9:00am, (GMT-08:00) America/Los

Reminder: Unix platform working group meeting (02/05 8AM PST) @ Wed Feb 5, 2020 8am - 9am (PST) When: Wednesday, 5 February 2020, 8:00am to 9:00am, (GMT-08:00) America/Los

Unix platform working group meeting (02/05 8AM PST) @ Wed Feb 5, 2020 8am - 9am (PST) When: Wednesday, 5 February 2020 8:00am to 9:00am (GMT-08:00) America/Los Angeles Where: webex Description: Hi

S-mode software needs a way to know memory used by SBI firmware so that it can correctly mark such memory as reserved. This patch was already posted on github as a PR [1], and I was told to send this

S-mode software needs a way to know memory used by SBI firmware so that it can correctly mark such memory as reserved. Related discussion: https://github.com/riscv/opensbi/issues/103 Signed-off-by:

Let's continue the discussion here as it has a wider audience than github PR. I have also cc'd all the possible stakeholders. The other alternatives propsed so far 1. Just parse the deveice tree

This patch adds SBI v0.2 compliant system reboot extension. It defines two functions: 1. sbi_reboot - A system reboot call with reboot type as parameter 2. sbi_shutdown - A system shutdown/poweroff

The words are misleading, as it could indicate that the above types only apply to RV32. The shutdown request Otherwise, looks good to me. Regards, Bin

Could this just be one function that had cold reboot, warm reboot, and shutdown all as options? Also: "This is a synchronous call and is not expected to return if succeeds." -> "This is a synchronous

One generic comment, pretty much similar to the SBI PMP extension I proposed, is that why is this necessary to introduce a new SBI extension to support reboot and shutdown? Do these functionalities

I am fine with merging shutdown into reboot call but I am not 100% convinced. Regarding the typo, I will update it. Regards, Anup

Doesn't QEMU already have a "SiFive Test Finisher" for this purpose?

Hello all, The assumption that there'll always be a PMP rule for marking the firmware's memory isn't always true. M-mode can access any region without a matching PMP rule so basically the firmware

The QEMU “SiFive Test Finisher” device has following issues: It is not a dedicated reboot/shutdown device. In fact, this device is meant to report test PASS or FAIL to QEMU users. It does not

There are different sorts of security threats to keep in mind. I'm generally not a fan of threat models where the "person who legally purchased the computer" is the threat, but that is admittedly a

This patch adds SBI v0.2 compliant system reboot extension. It defines the sbi_system_reboot function which does different things based on reboot_type parameter: 1. shutdown - Power-off the entire

> The System Reboot Extension provides a set of functions that allow the nit: "a set of functions" -> "a function"

Sure, I will fix this in next revision. Thanks for catching. Regards, Anup