From: Laszlo Ersek <lersek@redhat.com>
To: Pavel Hrdina <phrdina@redhat.com>
Cc: "Tom Lendacky" <thomas.lendacky@amd.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Michal Privoznik" <mprivozn@redhat.com>,
"qemu devel list" <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Brijesh Singh" <brijesh.singh@amd.com>
Subject: Re: firmware selection for SEV-ES
Date: Fri, 23 Apr 2021 15:06:49 +0200 [thread overview]
Message-ID: <17cd75db-98bf-7bf1-bc5b-cd71e62507ec@redhat.com> (raw)
In-Reply-To: <YILFNu1R8LcZRF48@antique-laptop>
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] <https://bugzilla.redhat.com/show_bug.cgi?id=1895035>
>>
>> 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
next prev parent reply other threads:[~2021-04-23 13:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 9:54 firmware selection for SEV-ES Laszlo Ersek
2021-04-21 11:51 ` Pavel Hrdina
2021-04-22 14:13 ` Laszlo Ersek
2021-04-23 8:16 ` Michal Privoznik
2021-04-23 10:31 ` Laszlo Ersek
2021-04-23 10:31 ` Pavel Hrdina
2021-04-23 12:34 ` Laszlo Ersek
2021-04-23 13:01 ` Pavel Hrdina
2021-04-23 13:06 ` Laszlo Ersek [this message]
2021-04-23 17:36 ` Pavel Hrdina
2021-04-26 11:01 ` Laszlo Ersek
2021-04-21 15:25 ` Tom Lendacky
2021-04-22 14:16 ` Laszlo Ersek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17cd75db-98bf-7bf1-bc5b-cd71e62507ec@redhat.com \
--to=lersek@redhat.com \
--cc=berrange@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=dgilbert@redhat.com \
--cc=mprivozn@redhat.com \
--cc=phrdina@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas.lendacky@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).