From: Brijesh Singh <brijesh.singh@amd.com>
To: "Liuchunyan (Chunyan, EULER)" <liuchunyan9@huawei.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v1 00/28] x86: Secure Encrypted Virtualization (AMD)
Date: Fri, 26 Aug 2016 10:38:03 -0500 [thread overview]
Message-ID: <36b191e2-c2b6-8e46-c0e3-98e2520d1be7@amd.com> (raw)
In-Reply-To: <B25DDC54236C3042A5DC90B7728884A6F1A269@SZXEMI504-MBX.china.huawei.com>
> Is there any production hardware supporting SEV? Which one? We
>
> are interested to do some test.
>
SEV support is not available in production hardware's. SEV support will
be available in future AMD hardware's.
>
>
> And, generally, I have a question about container protection. In
>
> white paper and also current KVM forum slides, it’s said this feature
>
> can protect containers from each other. If it could, it’s great! But I
>
> am not sure: the containers must be in a sandbox/VM? (that means,
>
> still need a virtualized environment). How about Common containers
>
> running directly on host OS?
>
SEV is integrated with existing AMD-V technology and can be used to
provide additional security of containers when running inside VM.
next parent reply other threads:[~2016-08-26 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B25DDC54236C3042A5DC90B7728884A6F1A269@SZXEMI504-MBX.china.huawei.com>
2016-08-26 15:38 ` Brijesh Singh [this message]
2016-08-22 23:23 [RFC PATCH v1 00/28] x86: Secure Encrypted Virtualization (AMD) Brijesh Singh
-- strict thread matches above, loose matches on Subject: below --
2016-08-22 23:21 Brijesh Singh
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=36b191e2-c2b6-8e46-c0e3-98e2520d1be7@amd.com \
--to=brijesh.singh@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuchunyan9@huawei.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).