linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Revanth Rajashekar <revanth.rajashekar@intel.com>
To: <linux-block@vger.kernel.org>
Cc: Jonathan Derrick <jonathan.derrick@intel.com>,
	Scott Bauer <sbauer@plzdonthack.me>,
	Jonas Rabenstine <jonas.rabenstein@studium.uni-erlangen.de>,
	David Kozub <zub@linux.fjfi.cvut.cz>,
	Jens Axboe <axboe@kernel.dk>
Subject: [PATCH v2 0/3] block: sed-opal: Generic Read/Write Opal Tables
Date: Tue, 15 Oct 2019 17:02:43 -0600	[thread overview]
Message-ID: <20191015230246.10171-1-revanth.rajashekar@intel.com> (raw)

This series of patches aims at extending SED Opal support:
1. Exposing enum opal_uid and opaluid definitions to the users to select
   the desired opal table UID.
2. Generalizing write data to any opal table
3. Add an IOCTL for reading/writing any Opal Table with Admin-1 authority

Datastore feature described in:
https://trustedcomputinggroup.org/wp-content/uploads/TCG_Storage-Opal_Feature_Set-Additional_DataStore_Tables_v1_00_r1_00_Final.pdf

Opal Application Note:
https://trustedcomputinggroup.org/wp-content/uploads/TCG_Storage_Opal_SSC_Application_Note_1-00_1-00-Final.pdf

This feature has been successfully tested on OPAL Datastore and MBR table using
internal tools with a Intel SSD and Intel Optane.

Changes from v1(https://lore.kernel.org/linux-block/20190821191051.3535-1-revanth.rajashekar@intel.com/):
	1. Fix the spelling mistake in the commit message.
	2. Introduce a length check condition before Copy To User in opal_read_table
	   function to facilitate user with easy debugging.
	3. Introduce switch cases in the opal_generic_read_write_table ioctl function.
	4. Move read/write table opal_step to discrete functions to reduce the load
	   on the ioctl function.
	5. Introduce 'opal table operations' enumeration in uapi.
	6. Remove tabs before the #defines in opal_read_write_table structure
           to improve the code readability

Revanth Rajashekar (3):
  block: sed-opal: Expose enum opal_uid and opaluid
  block: sed-opal: Generalizing write data to any opal table
  block: sed-opal: Add support to read/write opal tables generically

 block/opal_proto.h            |  39 ----
 block/sed-opal.c              | 375 ++++++++++++++++++++++------------
 include/linux/sed-opal.h      |   1 +
 include/uapi/linux/sed-opal.h | 132 ++++++++++++
 4 files changed, 373 insertions(+), 174 deletions(-)

--
2.17.1


             reply	other threads:[~2019-10-15 23:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 23:02 Revanth Rajashekar [this message]
2019-10-15 23:02 ` [PATCH v2 1/3] block: sed-opal: Expose enum opal_uid and opaluid Revanth Rajashekar
2019-10-16  6:31   ` Christoph Hellwig
2019-10-16 15:59     ` Rajashekar, Revanth
2019-10-15 23:02 ` [PATCH v2 2/3] block: sed-opal: Generalizing write data to any opal table Revanth Rajashekar
2019-10-16  6:32   ` Christoph Hellwig
2019-10-16 16:00     ` Rajashekar, Revanth
2019-10-15 23:02 ` [PATCH v2 3/3] block: sed-opal: Add support to read/write opal tables generically Revanth Rajashekar

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=20191015230246.10171-1-revanth.rajashekar@intel.com \
    --to=revanth.rajashekar@intel.com \
    --cc=axboe@kernel.dk \
    --cc=jonas.rabenstein@studium.uni-erlangen.de \
    --cc=jonathan.derrick@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=sbauer@plzdonthack.me \
    --cc=zub@linux.fjfi.cvut.cz \
    /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).