From: "Ni, Ray" <ray.ni@intel.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: "Gao, Liming" <liming.gao@intel.com>,
edk2-devel-groups-io <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-discuss] Design discussion for SEV-ES
Date: Wed, 11 Dec 2019 03:04:51 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5C398617@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <0a3d6c17-eca7-a7e0-bfba-5fe11449854a@amd.com>
Can you please have your slides ready in https://edk2.groups.io/g/devel/files/Designs/2019 before the meeting?
The earlier, the better.
How much time do you think it will need? I am thinking whether there is time for a second topic.
> -----Original Message-----
> From: Tom Lendacky <thomas.lendacky@amd.com>
> Sent: Tuesday, December 10, 2019 10:28 PM
> To: Ni, Ray <ray.ni@intel.com>
> Cc: Gao, Liming <liming.gao@intel.com>; edk2-devel-groups-io
> <devel@edk2.groups.io>; Kinney, Michael D <michael.d.kinney@intel.com>
> Subject: Re: [edk2-discuss] Design discussion for SEV-ES
>
> On 12/10/19 2:09 AM, Ni, Ray wrote:
> > Tom,
> > I may not in the discuss mailing list. Liming forwarded your request to me.
> Sorry I acked so late.
> >
> > This week's open design meeting is vacant. Is that still your plan to use this
> week's open design meeting to discuss SEV-ES?
>
> Yes, I would like to, if that still works for everyone.
>
> Thanks,
> Tom
>
> >
> > Thanks,
> > Ray
> >
> >> -----Original Message-----
> >> From: Gao, Liming <liming.gao@intel.com>
> >> Sent: Monday, November 25, 2019 9:18 PM
> >> To: Ni, Ray <ray.ni@intel.com>
> >> Subject: FW: [edk2-discuss] Design discussion for SEV-ES
> >>
> >> FYI
> >>
> >> -----Original Message-----
> >> From: discuss@edk2.groups.io <discuss@edk2.groups.io> On Behalf Of
> Tom
> >> Lendacky
> >> Sent: Thursday, November 21, 2019 4:22 AM
> >> To: discuss@edk2.groups.io
> >> Subject: [edk2-discuss] Design discussion for SEV-ES
> >>
> >> I'd like to be added to the TianoCore Design Meeting to discuss support
> >> SEV-ES in OVMF.
> >>
> >> Looking at the calendar, the meeting scheduled for December 12, 2019
> would
> >> be best.
> >>
> >> Discussion length will depend on how much everyone understands the
> >> current
> >> SEV support and the additional requirements of SEV-ES.
> >>
> >> Thank you,
> >> Tom Lendacky
> >>
> >>
> >
next prev parent reply other threads:[~2019-12-11 3:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <379ea894-4c55-c0e3-3c6f-7bed6862bac5@amd.com>
[not found] ` <4A89E2EF3DFEDB4C8BFDE51014F606A14E5482E4@SHSMSX104.ccr.corp.intel.com>
2019-12-10 8:09 ` [edk2-discuss] Design discussion for SEV-ES Ni, Ray
2019-12-10 14:28 ` Lendacky, Thomas
2019-12-11 3:04 ` Ni, Ray [this message]
2019-12-11 15:06 ` Lendacky, Thomas
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-list 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=734D49CCEBEEF84792F5B80ED585239D5C398617@SHSMSX104.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/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