From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id D531221A09104 for ; Tue, 23 May 2017 09:20:17 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 33CE063E34; Tue, 23 May 2017 16:20:17 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 33CE063E34 Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=lersek@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 33CE063E34 Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-123.phx2.redhat.com [10.3.116.123]) by smtp.corp.redhat.com (Postfix) with ESMTP id 8B63960F85; Tue, 23 May 2017 16:20:15 +0000 (UTC) To: Julien Grall , Konrad Rzeszutek Wilk , xen-devel@lists.xenproject.org, jbeulich@suse.com Cc: Gary Lin , Jordan Justen , edk2-devel-01 References: <20170506193023.4767-1-lersek@redhat.com> <20170508042759.kuut2vueabxvimwk@GaryWorkstation> <20170512020215.jvnmgzvrgdv66ere@GaryWorkstation> <12b9e870-30e4-8b88-9851-771d94264552@redhat.com> <149489525952.434.10185839319642314352@jljusten-skl> <20170516042034.hpf3fllcarzkgomh@GaryWorkstation> <5abcc684-72e4-990b-0682-7c163a7fc9cf@redhat.com> <20170523141200.GB29008@localhost.localdomain> <6af13bb5-0bfb-c9e3-e9fe-d1361d851e7d@arm.com> From: Laszlo Ersek Message-ID: <5a41b0c4-2d2c-de02-16e7-23d4806d7651@redhat.com> Date: Tue, 23 May 2017 18:20:14 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <6af13bb5-0bfb-c9e3-e9fe-d1361d851e7d@arm.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Tue, 23 May 2017 16:20:17 +0000 (UTC) Subject: Re: Is: Fix for 4MB BIOS payload in hvmloader. Was:Re: [PATCH 0/5] OvmfPkg: complete the 4MB flash image support ("-bios" / emulated variables) X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2017 16:20:18 -0000 Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit On 05/23/17 17:02, Julien Grall wrote: > Hi, > > On 23/05/17 15:12, Konrad Rzeszutek Wilk wrote: >>>> The primary location for reporting bugs against the hypervisor and >>>> associated bundled tools [...] is by posting to the xen-devel mailing >>>> list (list info). Please tag your subject line with a '[BUG]' prefix. >>>> Note that you do not need to be subscribed to the list to post >>>> (although non-subscribers are moderated this usually happens pretty >>>> quickly) and that list policy is to CC people so you shouldn't miss >>>> any replies. >>>> >>>> [...] >>>> >>>> Although a bugzilla instance does exist it is not well maintained or >>>> widely used by developers. If you really want to file a bug in >>>> bugzilla you are strongly recommended to also post to the mailing >>>> list. >>> >>> This does not make things easier for us, because rather than recurrently >>> check a simple bug status field in the Xen tracker, we'd have to be >>> tapped into Xen development, and follow the email thread & any relevant >>> commits closely. In reality I'm not even subscribed to xen-devel. > > We recently introduced a tracker ([1]) to help us following the state of > bugs/features. It is managed by maintainers and read-only for the others. > > The usual process is to report the bug on the mailing-list and a > maintainer will create a bug on the tracker if we have no immediate > solution. That's perfect; we'll be able to reference Xen issue reports with URLs like (just an example) , from TianoCore BZs. That should enable us to quickly re-check the state of the Xen report whenever we revisit the dependent TianoCore BZ. ... Can you please add the information about "xenproject.atlassian.net" to the Xen Wiki article at ? > In this case, the patch made rc6. So I believe the problem is resolved. Yes, it is. Thanks! Laszlo > Cheers, > > [1] https://xenproject.atlassian.net/projects/XEN/issues >