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=-3.5 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 A03ECC433B4 for ; Fri, 23 Apr 2021 13:09:05 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (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 1B62C61422 for ; Fri, 23 Apr 2021 13:09:05 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1B62C61422 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:34820 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lZvYO-0003sJ-2i for qemu-devel@archiver.kernel.org; Fri, 23 Apr 2021 09:09:04 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:59348) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lZvWS-0002fZ-B9 for qemu-devel@nongnu.org; Fri, 23 Apr 2021 09:07:04 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:22034) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lZvWM-0003Ny-7t for qemu-devel@nongnu.org; Fri, 23 Apr 2021 09:07:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1619183214; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CKbiJvO8D+qP9hfc7hFZ4uufMVS4nm6r8u9POdsfEs4=; b=K+bwOYt3m8yiGdu1GZMEWqtBcooogdNSFnh6nlqSNbqJmXK30uBRH6rHJRib9NzuCTFlpg 1/P4EeqhKoOPTb1NXtP0hx+jDSrc4a37pCA+J1RTD64uwp4KY9CWWJkp/SR0PfZryl/A3m qsRVHWBzI6qnEHlR6DCtjzTDGAydeok= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-100-EygDwtkrOYWD2jhV8yWnXQ-1; Fri, 23 Apr 2021 09:06:52 -0400 X-MC-Unique: EygDwtkrOYWD2jhV8yWnXQ-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BE6D3107ACCA; Fri, 23 Apr 2021 13:06:51 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-115-2.ams2.redhat.com [10.36.115.2]) by smtp.corp.redhat.com (Postfix) with ESMTP id 246875DEAD; Fri, 23 Apr 2021 13:06:49 +0000 (UTC) Subject: Re: firmware selection for SEV-ES To: Pavel Hrdina References: <6af8c5c7-6166-7f83-9ff0-4c24460577e2@redhat.com> <0b5d799c-6290-5585-599e-4c4f37af6202@redhat.com> <0cf69e7e-d159-6b68-0046-5449b0241634@redhat.com> From: Laszlo Ersek Message-ID: <17cd75db-98bf-7bf1-bc5b-cd71e62507ec@redhat.com> Date: Fri, 23 Apr 2021 15:06:49 +0200 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=170.10.133.124; envelope-from=lersek@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Tom Lendacky , "=?UTF-8?Q?Daniel_P._Berrang=c3=a9?=" , Michal Privoznik , qemu devel list , "Dr. David Alan Gilbert" , Brijesh Singh Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On 04/23/21 15:01, Pavel Hrdina wrote: > On Fri, Apr 23, 2021 at 02:34:02PM +0200, Laszlo Ersek wrote: >> On 04/23/21 12:31, Pavel Hrdina wrote: >>> On Fri, Apr 23, 2021 at 10:16:24AM +0200, Michal Privoznik wrote: >>>> On 4/22/21 4:13 PM, Laszlo Ersek wrote: >>>>> On 04/21/21 13:51, Pavel Hrdina wrote: >> >>>>> Should we file a libvirtd Feature Request (where?) for recognizing the >>>>> @amd-sev-es feature flag? >>>> >>>> Yes, we should. We can use RedHat bugzilla for that. Laszlo - do you want to >>>> do it yourself or shall I help you with that? >>> >>> This BZ looks like it's already tracking support for amd-sev-es [1]. >>> >>> Pavel. >>> >>> [1] >> >> That's a private RHBZ that tracks SEV-ES for a product that is different >> from "libvirt upstream". > > I didn't notice that's a private RHBZ, thanks for pointing it out. > > For upstream libvirt we no longer use RHBZ to track RFEs/BZs, we use > gitlab issues so if we want to track the work in upstream as well I can > create a new issue. Heh, I suspected I was missing something there :) Yes, please, if you or Michal could create a new issue in gitlab, that would be great. Thanks Laszlo