[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <69102fdf-221d-466b-16dd-c17e0ba0ab2f@intel.com>
Date: Sun, 22 Oct 2017 22:09:16 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
Cc: Christoph Hellwig <hch@...radead.org>, viro@...iv.linux.org.uk,
linux-kernel@...r.kernel.org, intel-sgx-kernel-dev@...ts.01.org,
platform-driver-x86@...r.kernel.org
Subject: Re: [intel-sgx-kernel-dev] [PATCH v4 06/12] fs/pipe.c: export
create_pipe_files() and replace_fd()
On 10/22/2017 07:55 PM, Jarkko Sakkinen wrote:
> On Fri, Oct 20, 2017 at 07:32:42AM -0700, Dave Hansen wrote:
>> I've always been curious, and the changelog and thread are curiously
>> oblique on this topic: what the heck does this driver use pipes *for*?
> For communication with the process hosting the launch enclave.
But, why pipes? Why does the kernel have to be the one setting these
up? Why is this communication necessary in the first place?
Powered by blists - more mailing lists