All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: virtio-dev@lists.oasis-open.org,
	Tomas Winkler <tomas.winkler@intel.com>,
	Yang Huang <yang.huang@intel.com>
Cc: Bing Zhu <bing.zhu@intel.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: [virtio-dev] VIRTIO RPMB Front End drivers for Linux
Date: Fri, 08 May 2020 17:11:36 +0100	[thread overview]
Message-ID: <87sgga4daf.fsf@linaro.org> (raw)


Hi,

I'm currently working on a vhost-user backend for virto-rpmb as defined
in the draft version of the OASIS spec (since 8c6acac2). I'm developing
it within the QEMU source tree but it is intended to be a portable
vhost-user binary with minimal POSIX like dependencies.

Part of the aim of the project is to experiment with a vhost-user
backend that has minimal access to guest memory and RPMB makes sense as
the vhost-user daemon only really needs to see the virt queues to pass
the data back and forth. One eventual architecture would be to move the
vhost-user driver into it's own isolated VM with only minimal memory
sharing between the guest and it's back-end.

I've gotten enough of the plumbing working now that I'm ready to start
implementing the RPMB spec itself. I've been looking for a front-end to
use in testing and I found the Linux driver sitting in Project ACRN's
guest kernel fork. With this kernel and VIRTIO_ID_RPMB tweaked to the
standard based one I get far enough that the driver is initialised
before my drivers falls over when an un-handled feature is requested
(0x130000000). This is slightly confusing because the spec doesn't
define any feature bits. So a few questions:

  - how divergent is the virtio-rpmb front/back-end in ACRN from the
    OASIS spec?

  - is there likely to be another submission to the upstream kernel?

I've also read the document on the ACRN website which talks about the
secure architecture:

  https://projectacrn.github.io/latest/tutorials/trustyACRN.html

I was wondering if there was any low level usage information. From
looking at the Kconfig options it seems the virtio-rpmb driver
interfaces with a wider RPMB sub-system which exposes a character device
to the kernels user-space. So:

  - are there any special user-space tools to use this interface?

  - is there a write-up somewhere of how to exercise the interface or
    any sort of test suite?

Thanks in advance,


-- 
Alex Bennée

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


             reply	other threads:[~2020-05-08 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 16:11 Alex Bennée [this message]
     [not found] ` <bb869ec95dc2479982e3390d650753d9@intel.com>
2020-05-28 19:47   ` [virtio-dev] Re: VIRTIO RPMB Front End drivers for Linux Alex Bennée

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=87sgga4daf.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=bing.zhu@intel.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=mst@redhat.com \
    --cc=tomas.winkler@intel.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=yang.huang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.