linux-kernel - [RFCv3 00/11] remoteproc: Support bi-directional vdev config space

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 16 Jan 2013 15:43:39 +0100
From:	sjur.brandeland@...ricsson.com
To:	Ido Yariv <ido@...ery.com>, Ohad Ben-Cohen <ohad@...ery.com>
Cc:	mporter@...com,
	Sjur Brændeland <sjurbren@...il.com>,
	linux-kernel@...r.kernel.org,
	Linus Walleij <linus.walleij@...aro.org>,
	Loic Pallardy <loic.pallardy@...ricsson.com>,
	Ludovic BARRE <ludovic.barre@...ricsson.com>,
	Fernando Guzman Lugo <fernando.lugo@...com>,
	Suman Anna <s-anna@...com>, Mark Grosen <mgrosen@...com>,
	Stephen Boyd <sboyd@...eaurora.org>,
	Sjur Brændeland <sjur.brandeland@...ricsson.com>
Subject: [RFCv3 00/11] remoteproc: Support bi-directional vdev config space

From: Sjur Brændeland <sjur.brandeland@...ricsson.com>

Changes since v2:
- Addressed review comments
- Reworked patch "Load firmware once". 

This patch-set is not yet thoroughly tested, but works in my
simulated environment.

This patch-set adds support for shared resource table between
Linux kernel and remote devices. 
- dynamically-allocated address of the vrings can be communicated
- vdev statuses can be communicated
- virtio config space becomes bi-directional
- virtio feature negotiation is two-way 
- Carveout can be allocated from start of device memory.
  dma_alloc_coherent() aligns to size of memory area. So if you e.g. 
  have 8Mb of memory, you cannot have carveout larger than 4Mb
  unless the carveout is allocated from start of the device memory
  area.

NOTE: This change is not backwards compatible with existing
device firmware! The memory allocation order changes. Previously
the Virtio Rings were always allocated at start of the share memory
area, but with this patch-set Virtio Rings are allocated after the
Carveouts. The address of the vrings are set in the resource table.

Cheers,
Sjur

Sjur Brændeland (11):
  remoteproc: Move enable_iommu to rproc_boot
  remoteproc: Code cleanup of resource parsing
  remoteproc: Move check on firmware name to rproc_add
  remoteproc: Refactor function rproc_elf_find_rsc_table
  remoteproc: Parse ELF file to find resource table address
  remoteproc: Parse STE-firmware and find resource table address
  remoteproc: Add state RPROC_LOADED
  remoteproc: Set vring addresses in resource table
  remoteproc: Load firmware once.
  remoteproc: Support virtio config space.
  remoteproc: Calculate max_notifyid by counting vrings

 drivers/remoteproc/remoteproc_core.c       |  264 +++++++++++++---------------
 drivers/remoteproc/remoteproc_debugfs.c    |    1 +
 drivers/remoteproc/remoteproc_elf_loader.c |   96 +++++++---
 drivers/remoteproc/remoteproc_internal.h   |   16 ++
 drivers/remoteproc/remoteproc_virtio.c     |   38 ++++-
 drivers/remoteproc/ste_modem_rproc.c       |   43 +++--
 include/linux/remoteproc.h                 |    7 +-
 7 files changed, 273 insertions(+), 192 deletions(-)

-- 
1.7.5.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/