All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: "Kwon, Gihwan" <gihwan.kwon@boeing.com>
Cc: xen-devel@lists.xenproject.org,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [QUESTION] Minimal Xen Configuration
Date: Wed, 02 Apr 2025 09:45:04 +0200	[thread overview]
Message-ID: <f4803fc17047a9d74928c66d39bf9632@bugseng.com> (raw)
In-Reply-To: <PH3P110MB2246A9D7AFA0A73000781B0390A0A@PH3P110MB2246.NAMP110.PROD.OUTLOOK.COM>

On 2025-03-28 07:43, Kwon, Gihwan wrote:
> Dear Xen Community,
> 
> I hope this message finds you well.
> 
> I have heard that there exists a minimal Xen configuration optimized 
> for
> safety-critical products, particularly in automotive applications, with 
> the
> code size reduced to approximately 50k SLOC.
> 
> Could anyone provide guidance or point me to relevant resources 
> regarding
> this minimal Xen configuration? Any insights or references would be 
> greatly
> appreciated.
> 
> Thank you in advance for your assistance.
> 
> Best regards,
> Gihwan Kwon

Hello,

I am part of the team that provides static analysis for Xen, mainly 
towards the objective to make Xen compliant with MISRA C guidelines. As 
part of that effort, a minimal Xen configuration has been defined (for 
Arm and x86_64) at [1], which is the one currently analyzed for static 
analysis for each commit [2]. It starts from the default configuration 
for the architecture (i.e., make defconfig) and then turns on or off 
various Kconfig options, as specified by EXTRA_XEN_CONFIG.

@Stefano Stabellini (Cc'ed) is the main driving force behind the Xen 
certification effort for automotive, therefore he's probably the best 
person to approach to get more information on this matter.

Hope this was helpful as a starting point.

Best Regards,
  Nicola Vetrini

[1] 
https://gitlab.com/xen-project/xen/-/blob/staging/automation/gitlab-ci/analyze.yaml?ref_type=heads
[2] https://gitlab.com/xen-project/hardware/xen/-/pipelines

-- 
Nicola Vetrini, B.Sc.
Software Engineer
BUGSENG (https://bugseng.com)
LinkedIn: https://www.linkedin.com/in/nicola-vetrini-a42471253


  reply	other threads:[~2025-04-02  7:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28  6:43 [QUESTION] Minimal Xen Configuration Kwon, Gihwan
2025-04-02  7:45 ` Nicola Vetrini [this message]
2025-04-02 21:09   ` Stefano Stabellini
2025-04-07  6:37     ` Kwon, Gihwan
2025-04-08  6:25       ` Kwon, Gihwan

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=f4803fc17047a9d74928c66d39bf9632@bugseng.com \
    --to=nicola.vetrini@bugseng.com \
    --cc=gihwan.kwon@boeing.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.