Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-27 Thread Bobby Eshleman
On Sat, Jan 25, 2020 at 05:11:18PM +, Andrew Cooper wrote: > On 25/01/2020 03:26, Bobby Eshleman wrote: > > On Fri, Jan 24, 2020 at 01:41:38PM +, Andrew Cooper wrote: > >> Other areas where you can reduce the minimum build would be to put some > >> defaults into the defconfig, such as

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-25 Thread Andrew Cooper
On 25/01/2020 03:26, Bobby Eshleman wrote: > On Fri, Jan 24, 2020 at 01:41:38PM +, Andrew Cooper wrote: >> On 22/01/2020 01:58, Bobby Eshleman wrote: >>> Currently, this patchset really only sets up virtual memory for Xen and >>> initializes UART to enable print output. None of RISC-V's >>>

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-24 Thread Bobby Eshleman
On Fri, Jan 24, 2020 at 01:41:38PM +, Andrew Cooper wrote: > On 22/01/2020 01:58, Bobby Eshleman wrote: > > Currently, this patchset really only sets up virtual memory for Xen and > > initializes UART to enable print output. None of RISC-V's > > virtualization support has been implemented

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-24 Thread Bobby Eshleman
On Thu, Jan 23, 2020 at 11:44:02PM +, Lars Kurth wrote: > If you add your name/email address to > https://cryptpad.fr/pad/#/2/pad/edit/D9vGzihPxxAOe6RFPz0sRCf+/ > I will CC > you on the next invite > They are usually the 1st

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-24 Thread Bobby Eshleman
On Thu, Jan 23, 2020 at 04:02:56PM +, Andrew Cooper wrote: > > We have https://gitlab.com/xen-project/xen/pipelines which runs a load > of containerised builds.  How easy is it to set up a containerised > RISC-V cross-compiler environment? > It's pretty easy. I personally use a Docker

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-24 Thread Andrew Cooper
On 22/01/2020 01:58, Bobby Eshleman wrote: > Currently, this patchset really only sets up virtual memory for Xen and > initializes UART to enable print output. None of RISC-V's > virtualization support has been implemented yet, although that is the > next road to start going down. Many functions

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-23 Thread Lars Kurth
> On 23 Jan 2020, at 05:31, Bobby Eshleman wrote: > > On Wed, Jan 22, 2020 at 04:27:39PM +, Lars Kurth wrote: >> >> You should also leverage the developer summit: see >> https://events.linuxfoundation.org/xen-summit/program/cfp/ >>

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-23 Thread Andrew Cooper
On 23/01/2020 05:19, Bobby Eshleman wrote: > On Wed, Jan 22, 2020 at 02:57:47PM +, Andrew Cooper wrote: >> How much time do you have to put towards the port?  Is this something in >> your free time, or something you are doing as part of work?  Ultimately, >> we are going to need to increase

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-23 Thread Alistair Francis
On Wed, 2020-01-22 at 14:57 +, Andrew Cooper wrote: > On 22/01/2020 01:58, Bobby Eshleman wrote: > > Hey everybody, > > > > This is an RFC patchset for the very beginnings of adding RISC-V > > support > > to Xen. This RFC is really just to start a dialogue about > > supporting > > RISC-V and

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-22 Thread Bobby Eshleman
On Wed, Jan 22, 2020 at 04:27:39PM +, Lars Kurth wrote: > > You should also leverage the developer summit: see > https://events.linuxfoundation.org/xen-summit/program/cfp/ > > CfP closes March 6th. Design sessions can be submitted

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-22 Thread Bobby Eshleman
On Wed, Jan 22, 2020 at 02:57:47PM +, Andrew Cooper wrote: > How much time do you have to put towards the port?  Is this something in > your free time, or something you are doing as part of work?  Ultimately, > we are going to need to increase the level of RISC-V knowledge in the > community

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-22 Thread Bobby Eshleman
On Wed, Jan 22, 2020 at 01:05:11PM -0800, Stefano Stabellini wrote: > On Wed, 22 Jan 2020, Andrew Cooper wrote: > > > My big questions are: > > > Does the Xen project have interest in RISC-V? > > > > There is very large downstream interest in RISC-V.  So a definite yes. > > Definite Yes from

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-22 Thread Stefano Stabellini
On Wed, 22 Jan 2020, Andrew Cooper wrote: > > My big questions are: > > Does the Xen project have interest in RISC-V? > > There is very large downstream interest in RISC-V.  So a definite yes. Definite Yes from me too > > What can be done to make the RISC-V port as upstreamable as > >

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-22 Thread Lars Kurth
> On 22 Jan 2020, at 14:57, Andrew Cooper wrote: > > On 22/01/2020 01:58, Bobby Eshleman wrote: >> Hey everybody, >> >> This is an RFC patchset for the very beginnings of adding RISC-V support >> to Xen. This RFC is really just to start a dialogue about supporting >> RISC-V and align with

Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-22 Thread Andrew Cooper
On 22/01/2020 01:58, Bobby Eshleman wrote: > Hey everybody, > > This is an RFC patchset for the very beginnings of adding RISC-V support > to Xen. This RFC is really just to start a dialogue about supporting > RISC-V and align with the Xen project and community before going > further. For that

[Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V

2020-01-21 Thread Bobby Eshleman
Hey everybody, This is an RFC patchset for the very beginnings of adding RISC-V support to Xen. This RFC is really just to start a dialogue about supporting RISC-V and align with the Xen project and community before going further. For that reason, it is very rough and very incomplete. My name