From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 482D1C32771 for ; Wed, 22 Jan 2020 21:05:32 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 0FE6F2465A for ; Wed, 22 Jan 2020 21:05:32 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="0UUZ2nLb" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0FE6F2465A Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1iuNBb-0001nK-Ej; Wed, 22 Jan 2020 21:05:15 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1iuNBZ-0001nF-WA for xen-devel@lists.xenproject.org; Wed, 22 Jan 2020 21:05:14 +0000 X-Inumbo-ID: e1ae2c38-3d5a-11ea-bd5f-12813bfff9fa Received: from mail.kernel.org (unknown [198.145.29.99]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id e1ae2c38-3d5a-11ea-bd5f-12813bfff9fa; Wed, 22 Jan 2020 21:05:13 +0000 (UTC) Received: from localhost (c-67-164-102-47.hsd1.ca.comcast.net [67.164.102.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 09D1E2467A; Wed, 22 Jan 2020 21:05:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1579727112; bh=oPaTIOVVDh8/IDkTDrps0S3weMbf1rotv25CnqXwvso=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=0UUZ2nLbib10tgqPakmUpmiH9aYXDz6obcyxLteJz3ZnQnT6Jc8KqLj3sqmCDEuI0 Co/WbLEoLm0JQOzwWzGv6q78RiNgD8CnvAt6k8CTrmjj9cijGjZUNSHXulAabCoad2 UmyT3BVlkEoEuGuw1/tbRDIZRWH0dltoTNQN/o8o= Date: Wed, 22 Jan 2020 13:05:11 -0800 (PST) From: Stefano Stabellini X-X-Sender: sstabellini@sstabellini-ThinkPad-T480s To: Andrew Cooper In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-1449927802-1579727112=:16648" Subject: Re: [Xen-devel] [RFC XEN PATCH 00/23] xen: beginning support for RISC-V X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Cc: Bobby Eshleman , Stefano Stabellini , Julien Grall , Wei Liu , Konrad Rzeszutek Wilk , George Dunlap , Ian Jackson , Bobby Eshleman , Dan Robertson , Alistair Francis , xen-devel@lists.xenproject.org Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1449927802-1579727112=:16648 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT 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 > > possible? > > Any major pitfalls? > > > > It would be great to hear all of your feedback. > > Both RISC-V and Power9 are frequently requested things, and both suffer > from the fact that, while we as a community would like them, the > upstream intersection of "people who know Xen" and "people who know > enough arch $X to do an initial port" is 0. > > This series clearly demonstrates a change in the status quo, and I think > a lot of people will be happy. > > To get RISC-V to being fully supported, we will ultimately need to get > hardware into the CI system, and an easy way for developers to test > changes.  Do you have any thoughts on production RISC-V hardware > (ideally server form factor) for the CI system, and/or dev boards which > might be available fairly cheaply? My understanding is that virtualization development for RISC-V is done on QEMU right now (which could still be hooked into the CI system if somebody wanted to do the work I think.) --8323329-1449927802-1579727112=:16648 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cHM6Ly9saXN0 cy54ZW5wcm9qZWN0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3hlbi1kZXZlbA== --8323329-1449927802-1579727112=:16648--