linux-kernel - Re: [PATCH] riscv: Add initial Xen guest support for RISC-V

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.22.394.2501141554170.2684657@ubuntu-linux-20-04-desktop>
Date: Tue, 14 Jan 2025 16:01:40 -0800 (PST)
From: Stefano Stabellini <sstabellini@...nel.org>
To: Milan Djokic <milandjokic1995@...il.com>
cc: linux-riscv@...ts.infradead.org, paul.walmsley@...ive.com, 
    palmer@...belt.com, aou@...s.berkeley.edu, jgross@...e.com, 
    sstabellini@...nel.org, oleksandr_tyshchenko@...m.com, 
    Slavisa.Petrovic@...rk.com, Milan.Djokic@...rk.com, 
    rafael.j.wysocki@...el.com, sunilvl@...tanamicro.com, 
    takakura@...inux.co.jp, linux-kernel@...r.kernel.org, 
    xen-devel@...ts.xenproject.org, iommu@...ts.linux.dev, 
    oleksii.kurochko@...il.com
Subject: Re: [PATCH] riscv: Add initial Xen guest support for RISC-V

+Oleksii

On Tue, 14 Jan 2025, Milan Djokic wrote:
> From: Slavisa Petrovic <Slavisa.Petrovic@...rk.com>
> 
> This patch introduces initial support for running RISC-V as a Xen guest.
> It provides the necessary infrastructure and stubs for Xen-specific
> operations. Key changes include:
> 
> - Modifications to the RISC-V kernel to integrate Xen-specific hypercalls
>   and interfaces, with function implementations stubbed for future work.
> - Introduction of Xen-specific headers for RISC-V, including event
>   handling, hypervisor interaction, and page management. Functions are
>   defined but not yet implemented.
> - Stub implementations for memory management, grant tables, and context
>   switching in the Xen environment, allowing further development and
>   integration.
> 
> Signed-off-by: Milan Djokic <Milan.Djokic@...rk.com>
> Signed-off-by: Slavisa Petrovic <Slavisa.Petrovic@...rk.com>

Hi Milan, Slavisa,

Thank you very much for your contribution! Which Xen tree are you using
for development? I am asking because RISC-V support in Xen is still in
the process of being upstreamed, and [1] is the tree that consolidates
all patches currently on the to-be-upstreamed list.  

While the specific Xen tree you are using is not particularly important
at this stage, and using [1] is not a requirement, I am asking because
it is essential to align on the hypervisor ABI, especially regarding any
details that have not yet been upstreamed. Specifically, is there
anything in this patch series that relies on features not yet upstream
in Xen?  

[1] https://gitlab.com/xen-project/people/olkur/xen/-/tree/latest?ref_type=heads