From: Paulina Szubarczyk <paulinaszubarczyk@gmail.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: sstabellini@kernel.org, ian.jackson@eu.citrix.com,
qemu-devel@nongnu.org, david.vrabel@citrix.com,
anthony.perard@citrix.com, xen-devel@lists.xenproject.org,
roger.pau@citrix.com
Subject: Re: [PATCH v4 1/2] Interface for grant copy operation in libs.
Date: Thu, 4 Aug 2016 12:27:29 +0200 [thread overview]
Message-ID: <57A31891.9060106@gmail.com> (raw)
In-Reply-To: <20160804093813.GB32096@citrix.com>
On 08/04/2016 11:38 AM, Wei Liu wrote:
> The code looks ok. I have two minor suggestions below.
>
> I would suggest changing the subject line to:
>
> libs/gnttab: introduce grant copy interface
>
> On Tue, Aug 02, 2016 at 04:06:29PM +0200, Paulina Szubarczyk wrote:
>> In a linux part an ioctl(gntdev, IOCTL_GNTDEV_GRANT_COPY, ..)
>> system call is invoked. In mini-os the operation is yet not
>> implemented. For the OSs that does not implement gnttab the
>> call of the grant copy operation causes abort.
>>
>> Signed-off-by: Paulina Szubarczyk <paulinaszubarczyk@gmail.com>
>> ---
>> Changes since v3:
>> - revert to cast from xengnttab_grant_copy_segment_t
>> to ioctl_gntdev_grant_copy.
>> - added compile-time check to compare the libs
>> xengnttab_grant_copy_segment_t with the ioctl structure.
>> The patch relies on Wei patch introducing XENGNTTAB_BUILD_BUG_ON
>> in libs/gnttab.
>
> I should resubmit that one soon.
>
>> ---
> [...]
>> + rc = ioctl(fd, IOCTL_GNTDEV_GRANT_COPY, ©);
>> + if (rc)
>> + {
>> + GTERROR(xgt->logger, "ioctl GRANT COPY failed %d ", errno);
>> + }
>
> Normally for a single statement you don't need {} around it.
>
> No need to resubmit just because of this patch. I can handle the subject
> line change, fix up the style issue and change the comment according to
> David's suggestion while committing if you don't object to any of them.
>
Ok, thank you.
> I won't commit this patch right away though. I will wait until the QEMU
> patch is acked because I would avoid committing things that have no
> users.
>
> If you end up submitting another version you can make those changes
> yourself.
>
>
> Wei.
>
Paulina
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-08-04 10:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 14:06 [PATCH v4 0/2] qemu-qdisk: Implementation of grant copy operation Paulina Szubarczyk
2016-08-02 14:06 ` [PATCH v4 1/2] Interface for grant copy operation in libs Paulina Szubarczyk
2016-08-03 14:36 ` David Vrabel
2016-08-04 9:38 ` Wei Liu
[not found] ` <57A20152.6030607@citrix.com>
2016-08-04 9:42 ` David Vrabel
[not found] ` <20160804093813.GB32096@citrix.com>
2016-08-04 10:27 ` Paulina Szubarczyk [this message]
2016-08-02 14:06 ` [PATCH v4 2/2] qdisk - hw/block/xen_disk: grant copy implementation Paulina Szubarczyk
2016-08-08 11:11 ` Roger Pau Monné
2016-08-08 11:34 ` Paulina Szubarczyk
2016-08-08 11:44 ` Paulina Szubarczyk
2016-08-09 16:56 ` Anthony PERARD
2016-08-09 17:34 ` Paulina Szubarczyk
2016-08-10 10:29 ` Anthony PERARD
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=57A31891.9060106@gmail.com \
--to=paulinaszubarczyk@gmail.com \
--cc=anthony.perard@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).