All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: "Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
	"Doug Goldstein" <cardoe@cardoe.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Alistair Francis" <alistair.francis@wdc.com>,
	"Bob Eshleman" <bobbyeshleman@gmail.com>,
	"Connor Davis" <connojdavis@gmail.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Julien Grall" <julien@xen.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH for 4.21 v7 0/4] RISC-V runtime detection of extenstions
Date: Thu, 20 Feb 2025 18:44:11 +0100	[thread overview]
Message-ID: <cover.1740071755.git.oleksii.kurochko@gmail.com> (raw)

Based on riscv,isa property of device tree file parse extenstions which are
available in CPU.

As a part of this feature, drop CONFIG_RISCV_ISA_RV64G and explicitly use
extensions 'i', 'm', 'a', 'zicsr', 'zifencei' as they are necessary for a work
if Xen and it should be true not only for RISC-V 64 (but also for 32 and 128).

Oleksii Kurochko (4):
  automation: drop debian:11-riscv64 container
  xen/riscv: drop CONFIG_RISCV_ISA_RV64G
  xen/riscv: make zbb as mandatory
  xen/riscv: identify specific ISA supported by cpu

 automation/gitlab-ci/build.yaml         |  14 -
 automation/scripts/containerize         |   1 -
 xen/arch/riscv/Kconfig                  |  18 -
 xen/arch/riscv/Makefile                 |   1 +
 xen/arch/riscv/arch.mk                  |  13 +-
 xen/arch/riscv/cpufeature.c             | 504 ++++++++++++++++++++++++
 xen/arch/riscv/include/asm/cpufeature.h |  59 +++
 xen/arch/riscv/setup.c                  |   3 +
 8 files changed, 573 insertions(+), 40 deletions(-)
 create mode 100644 xen/arch/riscv/cpufeature.c
 create mode 100644 xen/arch/riscv/include/asm/cpufeature.h

-- 
2.48.1



             reply	other threads:[~2025-02-20 17:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 17:44 Oleksii Kurochko [this message]
2025-02-20 17:44 ` [PATCH for 4.21 v7 1/4] automation: drop debian:11-riscv64 container Oleksii Kurochko
2025-02-21  8:35   ` Jan Beulich
2025-02-21 11:57     ` Oleksii Kurochko
2025-02-21 12:30       ` Jan Beulich
2025-02-21 17:04         ` Oleksii Kurochko
2025-02-21 12:31       ` Jan Beulich
2025-02-20 17:44 ` [PATCH for 4.21 v7 2/4] xen/riscv: drop CONFIG_RISCV_ISA_RV64G Oleksii Kurochko
2025-02-26 12:55   ` Jan Beulich
2025-02-20 17:44 ` [PATCH for 4.21 v7 3/4] xen/riscv: make zbb as mandatory Oleksii Kurochko
2025-02-26 12:58   ` Jan Beulich
2025-02-26 14:38     ` Oleksii Kurochko
2025-02-26 14:49       ` Jan Beulich
2025-02-26 17:16         ` Oleksii Kurochko
2025-02-20 17:44 ` [PATCH for 4.21 v7 4/4] xen/riscv: identify specific ISA supported by cpu Oleksii Kurochko
2025-02-21 17:02 ` [PATCH for 4.21 v7 0.5/4] xen/README: add compiler and binutils versions for RISCV-64 Oleksii Kurochko
2025-02-24 10:57   ` Jan Beulich
2025-02-24 15:52     ` 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=cover.1740071755.git.oleksii.kurochko@gmail.com \
    --to=oleksii.kurochko@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=bobbyeshleman@gmail.com \
    --cc=cardoe@cardoe.com \
    --cc=connojdavis@gmail.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --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.