From owner-freebsd-arm@freebsd.org Thu Oct 17 21:03:06 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3D30615D8D8 for ; Thu, 17 Oct 2019 21:03:06 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out.migadu.com (out.migadu.com [91.121.223.63]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.migadu.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46vM7r3dLGz3DtN for ; Thu, 17 Oct 2019 21:03:03 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: (Migadu outbound); Thu, 17 Oct 2019 21:03:01 +0000 Received: from wms0-eu-central.migadu.com (wms0-eu-central.migadu.com [139.162.159.86]) by out.migadu.com (Haraka/2.8.16) with ESMTPSA id 1F54909C-44FB-4C09-B023-048464D88750.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 verify=FAIL); Thu, 17 Oct 2019 21:03:00 +0000 MIME-Version: 1.0 Date: Thu, 17 Oct 2019 21:03:00 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: RainLoop/1.12.1 From: greg@unrelenting.technology Message-ID: <120f10da37ee104ea0fb82adeac59c63@unrelenting.technology> Subject: Re: EC2 ARM64 "bare metal" instances To: "Colin Percival" , freebsd-arm@freebsd.org In-Reply-To: <0100016dd57b89f3-034edaf3-4ae3-46f6-96ad-a3f0cf202c05-000000@email.amazonses.com> References: <0100016dd57b89f3-034edaf3-4ae3-46f6-96ad-a3f0cf202c05-000000@email.amazonses.com> DKIM-Signature: v=1; a=rsa-sha256; bh=WI7aHwUISwAdKRm2eC9cHiXxfYJ+zUrTcDAY2S9dPiQ=; c=relaxed/simple; d=unrelenting.technology; h=from:subject:date:to; s=default; b=aGXVQAhCyGgq1k/vmkalAKSsN6iO3a1f96u3L+Ph7KVY4MMvKuzprMOsnVH958C4CdV/oRLDATBoQ8YleR61jiabzbGdmTrlge7GcU8mHNk4A3UVFImp1usCTPfTS/w7soMT1dXp4N0/P7AwpXuqbHddKqdlnzzM+aOiMhTnA4s= X-Rspamd-Queue-Id: 46vM7r3dLGz3DtN X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=aGXVQAhC; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 91.121.223.63 as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-5.52 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:91.121.223.63]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[63.223.121.91.list.dnswl.org : 127.0.10.0]; FROM_NO_DN(0.00)[]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-2.52)[ip: (-9.85), ipnet: 91.121.0.0/16(-4.26), asn: 16276(1.51), country: FR(-0.00)]; ASN(0.00)[asn:16276, ipnet:91.121.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Oct 2019 21:03:06 -0000 October 16, 2019 7:51 PM, "Colin Percival" wrote:= =0A=0A> Hi ARM experts,=0A> =0A> FreeBSD does not currently boot on Amazo= n's recently released "bare metal"=0A> ARM64 instances. It might be usefu= l to get these working, since they're=0A> reasonably powered hardware (16= cores, 32 GB RAM) and should be able to run=0A> bhyve (that's the "bare = metal" part).=0A=0AI know bhyvearm64 only supports GICv3 right now, so I = wonder how bhyvearm64=0Ais going to interact with the GICv2m-on-GICv3 thi= ng they've done=0A(WTF are they smoking?!).. =0A=0A> I'm aware of a few p= atches these systems needed in order to work on Linux=0A=0ANetBSD got sup= port recently too (yes yes I'm checking dmesgd.nycbug quite often :D)=0A= =0Ahttps://github.com/NetBSD/src/commits?author=3Djaredmcneill=0A=0AAppar= ently "downstream ports" in general only have a single device, so this=0A= filtering thing doesn't have to be a Graviton quirk:=0Ahttps://github.com= /NetBSD/src/commit/5969d36d314e797f3ce439a3fd445e5ba9d268f1=0A=0ABut we d= o need the AMZN0001 thing and the GIC thing.