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=-0.5 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED 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 5EA75C432C0 for ; Thu, 21 Nov 2019 22:07:35 +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 26D8B206CB for ; Thu, 21 Nov 2019 22:07:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="WlvRpp+L" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 26D8B206CB Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=invisiblethingslab.com 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 1iXuba-0006JB-1p; Thu, 21 Nov 2019 22:07:14 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1iXubZ-0006J6-18 for xen-devel@lists.xenproject.org; Thu, 21 Nov 2019 22:07:13 +0000 X-Inumbo-ID: 449e0a6a-0cab-11ea-adbe-bc764e2007e4 Received: from out3-smtp.messagingengine.com (unknown [66.111.4.27]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 449e0a6a-0cab-11ea-adbe-bc764e2007e4; Thu, 21 Nov 2019 22:07:11 +0000 (UTC) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id AF0D621C7D; Thu, 21 Nov 2019 17:07:11 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Thu, 21 Nov 2019 17:07:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=um6JSZ DQEaT3NxH+BS77Niy1g353ib4JQ9VwKh5cUEg=; b=WlvRpp+LYLAD0hpyiN48Ui /fhdmiOcQLLr8ESusEhN5+4oXbHLE7XmXjN2Wlbwjd5ptyUOUPozfB+yWYk90fGo J+vCyZJaejpRyzmFDJyi+RGbOXf32PI8Ydms6k5AYaxH05rDv6O+jwf90/vyMszD aWl+g5vWAIJOqO6QPVcS06p6ZU6YcB4YwPSAHOmC3rPOwKjdd4n/2jLaSUHsIV+c iJF+a98YFQu/WoozAppnJsDX4lJfGwwamIve3spooMvWXaA75rfMnWBd5blf7T42 29nGlDMuLO3cFZs9zXK2u81HJR/dB0tANv88fQ4cRYuVX+6PbypCpAT8lfl86LaQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudehvddgudehkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkfhggtggujgesghdtreertddtjeenucfhrhhomhepofgrrhgv khcuofgrrhgtiiihkhhofihskhhiqdfikphrvggtkhhiuceomhgrrhhmrghrvghksehinh hvihhsihgslhgvthhhihhnghhslhgrsgdrtghomheqnecuffhomhgrihhnpeigvghnrdho rhhgnecukfhppeegiedrudekledrvdekrdehjeenucfrrghrrghmpehmrghilhhfrhhomh epmhgrrhhmrghrvghksehinhhvihhsihgslhgvthhhihhnghhslhgrsgdrtghomhenucev lhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from mail-itl (unknown [46.189.28.57]) by mail.messagingengine.com (Postfix) with ESMTPA id C26C63060057; Thu, 21 Nov 2019 17:07:08 -0500 (EST) Date: Thu, 21 Nov 2019 23:07:04 +0100 From: Marek =?utf-8?Q?Marczykowski-G=C3=B3recki?= To: Roman Shaposhnik Message-ID: <20191121220704.GA2012@mail-itl> References: <0ba2bc19-2388-5fdc-43bd-3ac39497291c@suse.com> <91d6b37f-6f83-183d-6b1e-297c0381af75@citrix.com> MIME-Version: 1.0 In-Reply-To: Subject: Re: [Xen-devel] Status of 4.13 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: =?utf-8?B?SsO8cmdlbiBHcm/Dnw==?= , Wei Liu , George Dunlap , Andrew Cooper , Ian Jackson , Julien Grall , Jan Beulich , "xen-devel@lists.xenproject.org" Content-Type: multipart/mixed; boundary="===============5462364965890632648==" Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" --===============5462364965890632648== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="UlVJffcvxoiEqYs2" Content-Disposition: inline --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: [Xen-devel] Status of 4.13 On Thu, Nov 21, 2019 at 11:39:14AM -0800, Roman Shaposhnik wrote: > On Thu, Nov 21, 2019 at 9:38 AM Andrew Cooper = wrote: > > > > On 21/11/2019 17:31, Roman Shaposhnik wrote: > > > On Wed, Nov 20, 2019 at 10:06 PM J=C3=BCrgen Gro=C3=9F wrote: > > >> Where do we stand with Xen 4.13 regarding blockers and related patch= es? > > >> > > >> 1. OSStest failure regarding nested test: > > >> I'm not quite sure whether the currently debated patch of Andrew= is > > >> fixing the problem. If not, do we know what is missing or how to > > >> address the issue? If yes, could we please come to an agreement? > > >> As an alternative: any thoughts about ignoring this test failure= for > > >> 4.13-RC3 (IOW: doing a force push)? > > >> > > >> 2. Ryzen/Rome failures with Windows guests: > > >> What is the currently planned way to address the problem? Who is > > >> working on that? > > >> > > >> 3. Pending patches for 4.13: > > >> Could I please have feedback which patches tagged as "for-4.13" = are > > >> fixing real regressions or issues? I don't want to take any patc= hes > > >> not fixing real problems after RC3, and I hope to be able to get= a > > >> push rather sooner than later to be able to let Ian cut RC3. > > >> > > >> 4. Are there any blockers for 4.13 other than 1. and 2. (apart of any > > >> pending XSAs)? > > > Any chance the efi=3Dno-rs regression can be added to the list? I und= erstand > > > that I'm still on the hook to provide more details (I promise to do i= t on Fri > > > when I get to my lab to actually have a serial console on all these b= oxes). > > > At the same time this is a pretty serious regression for an entire cl= ass of > > > devices where Xen was perfectly happy even during RC1. > > > > https://xenbits.xen.org/gitweb/?p=3Dxen.git;a=3Dcommitdiff;h=3D534f9e29= ce28580892b3856036b5e5cd805667cc > > has been committed. It is in staging, but not in master yet (because > > master is blocked by my regression in 1). >=20 > I'll make sure to test it on Fri, but here's where I'm lost -- my > understanding that > activation of this patch requires a special build flag to be passed. > Which means, > we're still very much in a regresses state when it comes to building > out-of-the-box, > no? No, there are two thing: 1. A bug triggered by efi=3Dno-rs flag - fixed in the above commit 2. A second commit making efi=3Dno-rs unnecessary on some machines - this is what require build flag (CONFIG_EFI_SET_VIRTUAL_ADDRESS_MAP=3Dy). --=20 Best Regards, Marek Marczykowski-G=C3=B3recki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAl3XCogACgkQ24/THMrX 1yx2WAf/YxzJbL9b3XBs4PJtxlek6HKZbXhxU2uytIGbqEwL1gkuLPfFWgekKJYc mpQH1Fcdv94brszVsGzJaQVxHFH7isl0Pwq+hA3/ikN1XHlBJkzQjZm/cX9Z9KZU HRyF1Ij5xvNQG8lipwQmTPFkbx8gZPm0P9c5W7p9LdXE6hZXcxnx3/ycWOzwaorP GT4kqLX+wa+ZKXbqzj8my4LyywBscfemEhR//6OzoycfpCMN+de/KyS8wjdMfVM+ TeJ/PBIbzTcl0ONmR9d+SoxIs7suvFSLaTlGB5LPUuw/e97sjkhChQkeo6hdcLpA 659Z8ZURFW15i0gEi1HPAxS5+gMW9Q== =yTpT -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2-- --===============5462364965890632648== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cHM6Ly9saXN0 cy54ZW5wcm9qZWN0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3hlbi1kZXZlbA== --===============5462364965890632648==--