linux-sgx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, linux-sgx@vger.kernel.org,
	Dave Hansen <dave.hansen@linux.intel.com>,
	nathaniel@profian.com, Michael Kerrisk <mtk.manpages@gmail.com>,
	Reinette Chatre <reinette.chatre@intel.com>
Subject: Re: [PATCH v11] sgx.7: New page with overview of Software Guard eXtensions (SGX)
Date: Fri, 28 Jan 2022 03:19:18 +0200	[thread overview]
Message-ID: <YfNElmmBbkw1Xpfy@iki.fi> (raw)
In-Reply-To: <c58f3951-282c-ef66-fc62-844da06c5af4@gmail.com>

On Fri, Dec 17, 2021 at 02:50:56AM +0100, Alejandro Colomar (man-pages) wrote:
> Hi Jarkko,
> 
> Please see some comments below.
> 
> Thanks,
> Alex

Thank you. I've addressed all the comments below. However, I feel that
/dev/sgx_provision is not properly documented at all. I also think that
Reinette's argument for v10 was fair that "remove VEPC" ioctl that QEMU
uses should not be left out from the initial patch set.

I'm implementing user space that doest attestation, so I rather write a
proper description of the attestation, once it is working, rather than add
to the number of review rounds.

BR, Jarkko

  reply	other threads:[~2022-01-28  1:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-11 15:33 [PATCH v11] sgx.7: New page with overview of Software Guard eXtensions (SGX) Jarkko Sakkinen
2021-12-17  1:50 ` Alejandro Colomar (man-pages)
2022-01-28  1:19   ` Jarkko Sakkinen [this message]
2022-02-09 20:19     ` Alejandro Colomar (man-pages)
2022-02-20 20:05       ` Jarkko Sakkinen
2023-03-30 22:29         ` Alejandro Colomar
2023-04-21 21:13           ` Jarkko Sakkinen

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=YfNElmmBbkw1Xpfy@iki.fi \
    --to=jarkko@kernel.org \
    --cc=alx.manpages@gmail.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-sgx@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=nathaniel@profian.com \
    --cc=reinette.chatre@intel.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).