xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Connor Davis <connojdavis@gmail.com>
To: Alistair Francis <alistair23@gmail.com>
Cc: "open list:X86" <xen-devel@lists.xenproject.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	George Dunlap <george.dunlap@citrix.com>,
	Ian Jackson <iwj@xenproject.org>, Jan Beulich <jbeulich@suse.com>,
	Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
	Paul Durrant <paul@xen.org>,
	Tamas K Lengyel <tamas@tklengyel.com>,
	Alexandru Isaila <aisaila@bitdefender.com>,
	Petre Pircalabu <ppircalabu@bitdefender.com>,
	Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [PATCH v2 0/5] Minimal build for RISCV
Date: Fri, 14 May 2021 08:02:35 -0600	[thread overview]
Message-ID: <3d2e6213-3b38-1329-cb78-0e964577eb84@gmail.com> (raw)
In-Reply-To: <CAKmqyKN1+we16d3AkYg9GLXxic-Y=JZKdjqHfE5JRJTaGmaaHw@mail.gmail.com>


On 5/13/21 10:43 PM, Alistair Francis wrote:
> On Fri, May 14, 2021 at 2:18 PM Connor Davis <connojdavis@gmail.com> wrote:
>> Hi all,
>>
>> This series introduces a minimal build for RISCV. It is based on Bobby's
>> previous work from last year[0]. I have worked to rebase onto current Xen,
>> as well as update the various header files borrowed from Linux.
>>
>> This series provides the patches necessary to get a minimal build
>> working. The build is "minimal" in the sense that 1) it uses a
>> minimal config and 2) files, functions, and variables are included if
>> and only if they are required for a successful build based on the
>> config. It doesn't run at all, as the functions just have stub
>> implementations.
>>
>> My hope is that this can serve as a useful example for future ports as
>> well as inform the community of exactly what is imposed by common code
>> onto new architectures.
>>
>> The first 3 patches are mods to non-RISCV bits that enable building a
>> config with:
>>
>>    !CONFIG_HAS_NS16550
>>    !CONFIG_HAS_PASSTHROUGH
>>    !CONFIG_GRANT_TABLE
>>
>> respectively. The fourth patch adds the RISCV files, and the last patch
>> adds a docker container for doing the build. To build from the docker
>> container (after creating it locally), you can run the following:
>>
>>    $ make XEN_TARGET_ARCH=riscv64 SUBSYSTEMS=xen
>>
>> The sources taken from Linux are documented in arch/riscv/README.sources.
>> There were also some files copied from arm:
>>
>>    asm-arm/softirq.h
>>    asm-arm/random.h
>>    asm-arm/nospec.h
>>    asm-arm/numa.h
>>    asm-arm/p2m.h
>>    asm-arm/delay.h
>>    asm-arm/debugger.h
>>    asm-arm/desc.h
>>    asm-arm/guest_access.h
>>    asm-arm/hardirq.h
>>    lib/find_next_bit.c
>>
>> I imagine some of these will want some consolidation, but I put them
>> under the respective RISCV directories for now.
> Awesome!
>
> Do you have a public branch I could pull these from to try out?
>
> Alistair
Yes you can find the latest here: 
https://gitlab.com/connojd/xen/-/commits/riscv-build


Thanks,

Connor



      reply	other threads:[~2021-05-14 14:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14  4:17 Connor Davis
2021-05-14  4:17 ` [PATCH v2 1/5] xen/char: Default HAS_NS16550 to y only for X86 and ARM Connor Davis
2021-05-14  5:34   ` Elliott Mitchell
2021-05-14 14:13     ` Connor Davis
2021-05-14  4:17 ` [PATCH v2 2/5] xen/common: Guard iommu symbols with CONFIG_HAS_PASSTHROUGH Connor Davis
2021-05-14  4:17 ` [PATCH v2 3/5] xen: Fix build when !CONFIG_GRANT_TABLE Connor Davis
2021-05-14  4:17 ` [PATCH v2 4/5] xen: Add files needed for minimal riscv build Connor Davis
2021-05-14  9:46   ` Julien Grall
2021-05-14 13:57     ` Connor Davis
2021-05-14  4:17 ` [PATCH v2 5/5] automation: add container for riscv64 builds Connor Davis
2021-05-14  4:43 ` [PATCH v2 0/5] Minimal build for RISCV Alistair Francis
2021-05-14 14:02   ` Connor Davis [this message]

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=3d2e6213-3b38-1329-cb78-0e964577eb84@gmail.com \
    --to=connojdavis@gmail.com \
    --cc=aisaila@bitdefender.com \
    --cc=alistair23@gmail.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=george.dunlap@citrix.com \
    --cc=iwj@xenproject.org \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=paul@xen.org \
    --cc=ppircalabu@bitdefender.com \
    --cc=sstabellini@kernel.org \
    --cc=tamas@tklengyel.com \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    --subject='Re: [PATCH v2 0/5] Minimal build for RISCV' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).