From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: tpmdd-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org,
jarkko.sakkinen@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] tpm: vtpm_proxy: Implement new ioctl to get supported flags
Date: Thu, 4 May 2017 13:33:41 -0400 [thread overview]
Message-ID: <08065914-2b96-ca1d-2fe0-344472ed9691@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170504173130.GA20449@obsidianresearch.com>
On 05/04/2017 01:31 PM, Jason Gunthorpe wrote:
> On Thu, May 04, 2017 at 01:28:17PM -0400, Stefan Berger wrote:
>
>>> So allowing request_locality to fail from userspace seems reasonable.
>> What's the best interface to use for this ?
> If locality support is enabled then send a request locality packet to
> userspace and block until return, just like command execution?
We would have to invent a command for that...
next prev parent reply other threads:[~2017-05-04 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 14:56 [PATCH v3 0/3] Extend the vTPM proxy driver to pass locality Stefan Berger
[not found] ` <1493909787-1848-1-git-send-email-stefanb-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-05-04 14:56 ` [PATCH v3 1/3] tpm: vtpm_proxy: Implement new ioctl to get supported flags Stefan Berger
[not found] ` <1493909787-1848-2-git-send-email-stefanb-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-05-04 15:34 ` Jason Gunthorpe
2017-05-04 17:13 ` Stefan Berger
2017-05-04 17:20 ` Jason Gunthorpe
2017-05-04 17:28 ` Stefan Berger
2017-05-04 17:31 ` Jason Gunthorpe
2017-05-04 17:33 ` Stefan Berger [this message]
2017-05-04 14:56 ` [PATCH v3 2/3] tpm: vtpm_proxy: Implement request_locality function Stefan Berger
2017-05-04 14:56 ` [PATCH v3 3/3] tpm: vtpm_proxy: Add flag for ioctl to request locality prepended to command Stefan Berger
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=08065914-2b96-ca1d-2fe0-344472ed9691@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).