From: Stefan Hajnoczi <stefanha@gmail.com>
To: Ashish Mittal <ashmit602@gmail.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, kwolf@redhat.com,
armbru@redhat.com, berrange@redhat.com,
ashish.mittal@veritas.com, Ketan.Nilangekar@veritas.com,
Abhijit.Dey@veritas.com
Subject: Re: [Qemu-devel] [PATCH v2 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support
Date: Wed, 10 Aug 2016 15:32:02 +0100 [thread overview]
Message-ID: <20160810143202.GA22780@stefanha-x1.localdomain> (raw)
In-Reply-To: <1470621661-21877-1-git-send-email-ashish.mittal@veritas.com>
[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]
On Sun, Aug 07, 2016 at 07:01:01PM -0700, Ashish Mittal wrote:
> This patch adds support for a new block device type called "vxhs".
> Source code for the library that this code loads can be downloaded from:
> https://github.com/MittalAshish/libqnio.git
>
> Version 2 patch submission fixes the following issues:
> (1) Removed code to dlopen library. We now check if libqnio is installed during
> configure, and directly link with it.
> (2) Changed file headers to mention GPLv2-or-later license.
> (3) Removed unnecessary type casts and inlines.
> (4) Removed custom tokenize function and modified code to use g_strsplit.
> (5) Replaced malloc/free with g_new/g_free and removed code that checks for
> memory allocation failure conditions.
> (6) Removed some block ops implementations that were place-holders only.
> (7) Removed all custom debug messages. Added new messages in block/trace-events
> (8) Other miscellaneous corrections.
>
> TODO: QAPI changes and (fixes to) review comments from Stefan.
> Signed-off-by: Ashish Mittal <ashish.mittal@veritas.com>
> ---
> block/Makefile.objs | 2 +
> block/trace-events | 40 ++
> block/vxhs.c | 1199 +++++++++++++++++++++++++++++++++++++++++++++++++++
> block/vxhs.h | 294 +++++++++++++
> configure | 50 +++
> 5 files changed, 1585 insertions(+)
> create mode 100644 block/vxhs.c
> create mode 100644 block/vxhs.h
I'll review v3 with the issues I raised addressed.
Please put the patch changelog below the '---' line. This way the
changelog is not included in the git history when the patch is merged.
The changelog is only useful while the patch is being discussed on the
mailing list but shouldn't be included in the git-log(1) output.
Typically it looks like this:
---
v2:
* Removed code to dlopen library. We now check if libqnio is installed
during configure, and directly link with it.
...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-08-10 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 2:01 [Qemu-devel] [PATCH v2 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support Ashish Mittal
2016-08-08 9:10 ` Daniel P. Berrange
2016-08-10 14:32 ` Stefan Hajnoczi [this message]
2016-08-11 15:00 ` Kevin Wolf
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=20160810143202.GA22780@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=Abhijit.Dey@veritas.com \
--cc=Ketan.Nilangekar@veritas.com \
--cc=armbru@redhat.com \
--cc=ashish.mittal@veritas.com \
--cc=ashmit602@gmail.com \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).