From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Oleksii Kurochko <oleksii.kurochko@gmail.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] RISCV/shutdown: Implement machine_{halt,restart}()
Date: Tue, 3 Sep 2024 15:27:43 +0100 [thread overview]
Message-ID: <7d2c4b4a-e366-4f95-9e41-1eb4439d1333@citrix.com> (raw)
In-Reply-To: <1ace3e56-9cd8-4828-aaa2-92ba7766945a@suse.com>
On 03/09/2024 3:26 pm, Jan Beulich wrote:
> On 03.09.2024 16:19, Andrew Cooper wrote:
>> SBI has an API for shutdown so wire it up. However, the spec does allow the
>> call not to be implemented, so we have to cope with the call return returning.
>>
>> There is a reboot-capable SBI extention, but in the short term route route
>> machine_restart() into machine_halt().
>>
>> Then, use use machine_halt() rather than an infinite loop at the end of
>> start_xen(). This avoids the Qemu smoke test needing to wait for the full
>> timeout in order to succeed.
>>
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Acked-by: Jan Beulich <jbeulich@suse.com>
Thanks.
> ideally with ...
>
>> --- /dev/null
>> +++ b/xen/arch/riscv/shutdown.c
>> @@ -0,0 +1,25 @@
>> +/* SPDX-License-Identifier: GPL-2.0-or-later */
>> +#include <xen/shutdown.h>
>> +
>> +#include <asm/sbi.h>
>> +
>> +void machine_halt(void)
>> +{
>> + sbi_shutdown();
>> +
>> + for ( ;; )
>> + asm volatile ("wfi");
> ... the missing blanks added here, as you move that loop around.
Ah yes. Will do.
~Andrew
next prev parent reply other threads:[~2024-09-03 14:27 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 17:01 [PATCH v6 0/9] RISCV device tree mapping Oleksii Kurochko
2024-09-02 17:01 ` [PATCH v6 1/9] xen/riscv: prevent recursion when ASSERT(), BUG*(), or panic() are called Oleksii Kurochko
2024-09-03 14:19 ` [PATCH] RISCV/shutdown: Implement machine_{halt,restart}() Andrew Cooper
2024-09-03 14:23 ` Andrew Cooper
2024-09-03 14:27 ` Jan Beulich
2024-09-03 14:26 ` Jan Beulich
2024-09-03 14:27 ` Andrew Cooper [this message]
2024-09-04 10:22 ` oleksii.kurochko
2024-09-10 9:42 ` [PATCH v6 1/9] xen/riscv: prevent recursion when ASSERT(), BUG*(), or panic() are called Jan Beulich
2024-09-10 13:55 ` oleksii.kurochko
2024-09-02 17:01 ` [PATCH v6 2/9] xen/riscv: use {read,write}{b,w,l,q}_cpu() to define {read,write}_atomic() Oleksii Kurochko
2024-09-03 14:21 ` Andrew Cooper
2024-09-04 10:27 ` oleksii.kurochko
2024-09-04 10:31 ` Andrew Cooper
2024-09-05 15:45 ` oleksii.kurochko
2024-09-02 17:01 ` [PATCH v6 3/9] xen/riscv: allow write_atomic() to work with non-scalar types Oleksii Kurochko
2024-09-10 9:53 ` Jan Beulich
2024-09-10 15:28 ` oleksii.kurochko
2024-09-10 16:05 ` Jan Beulich
2024-09-11 11:34 ` oleksii.kurochko
2024-09-11 11:49 ` Jan Beulich
2024-09-12 11:15 ` oleksii.kurochko
2024-09-12 11:41 ` oleksii.kurochko
2024-09-02 17:01 ` [PATCH v6 4/9] xen/riscv: set up fixmap mappings Oleksii Kurochko
2024-09-10 10:01 ` Jan Beulich
2024-09-10 15:55 ` oleksii.kurochko
2024-09-10 16:07 ` Jan Beulich
2024-09-02 17:01 ` [PATCH v6 5/9] xen/riscv: introduce asm/pmap.h header Oleksii Kurochko
2024-09-02 17:01 ` [PATCH v6 6/9] xen/riscv: introduce functionality to work with CPU info Oleksii Kurochko
2024-09-10 10:33 ` Jan Beulich
2024-09-11 12:05 ` oleksii.kurochko
2024-09-11 12:14 ` Jan Beulich
2024-09-12 9:27 ` oleksii.kurochko
2024-09-12 9:58 ` Jan Beulich
2024-09-12 16:02 ` oleksii.kurochko
2024-09-13 12:51 ` Jan Beulich
2024-09-02 17:01 ` [PATCH v6 7/9] xen/riscv: introduce and initialize SBI RFENCE extension Oleksii Kurochko
2024-09-10 11:32 ` Jan Beulich
2024-09-02 17:01 ` [PATCH v6 8/9] xen/riscv: page table handling Oleksii Kurochko
2024-09-10 12:19 ` Jan Beulich
2024-09-11 15:09 ` oleksii.kurochko
2024-09-02 17:01 ` [PATCH v6 9/9] xen/riscv: introduce early_fdt_map() Oleksii Kurochko
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=7d2c4b4a-e366-4f95-9e41-1eb4439d1333@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=oleksii.kurochko@gmail.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.