From: Paulina Szubarczyk <paulinaszubarczyk@gmail.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
ian.jackson@eu.citrix.com, david.vrabel@citrix.com,
anthony.perard@citrix.com, xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 2/2] qdisk - hw/block/xen_disk: grant copy implementation
Date: Tue, 19 Jul 2016 12:12:22 +0200 [thread overview]
Message-ID: <578DFD06.9000507@gmail.com> (raw)
In-Reply-To: <20160719091209.ftmwfg4bm5hfhlxf@mac>
On 07/19/2016 11:12 AM, Roger Pau Monné wrote:
> On Wed, Jun 22, 2016 at 10:38:53AM +0200, Paulina Szubarczyk wrote:
>> Copy data operated on during request from/to local buffers to/from
>> the grant references.
>>
>> Before grant copy operation local buffers must be allocated what is
>> done by calling ioreq_init_copy_buffers. For the 'read' operation,
>> first, the qemu device invokes the read operation on local buffers
>> and on the completion grant copy is called and buffers are freed.
>> For the 'write' operation grant copy is performed before invoking
>> write by qemu device.
>>
>> A new value 'feature_grant_copy' is added to recognize when the
>> grant copy operation is supported by a guest.
>> The body of the function 'ioreq_runio_qemu_aio' is moved to
>> 'ioreq_runio_qemu_aio_blk' and in the 'ioreq_runio_qemu_aio' depending
>> on the support for grant copy according checks, initialization, grant
>> operation are made, then the 'ioreq_runio_qemu_aio_blk' function is
>> called.
>>
>> Signed-off-by: Paulina Szubarczyk <paulinaszubarczyk@gmail.com>
>> ---
>> Changes since v2:
>> - to use the xengnttab_* function directly added -lxengnttab to configure
>> and include <xengnttab.h> in include/hw/xen/xen_common.h
>> - in ioreq_copy removed an out path, changed a log level, made explicit
>> assignement to 'xengnttab_copy_grant_segment'
>> * I did not change the way of testing if grant_copy operation is implemented.
>> As far as I understand if the code from gnttab_unimp.c is used then the gnttab
>> device is unavailable and the handler to gntdev would be invalid. But
>> if the handler is valid then the ioctl should return operation unimplemented
>> if the gntdev does not implement the operation.
>>
>> configure | 2 +-
>> hw/block/xen_disk.c | 171 ++++++++++++++++++++++++++++++++++++++++----
>> include/hw/xen/xen_common.h | 2 +
>> 3 files changed, 162 insertions(+), 13 deletions(-)
>
> [...]
>
>> @@ -1020,10 +1160,17 @@ static int blk_connect(struct XenDevice *xendev)
>>
>> xen_be_bind_evtchn(&blkdev->xendev);
>>
>> + blkdev->feature_grant_copy =
>> + (xengnttab_grant_copy(blkdev->xendev.gnttabdev, 0, NULL) == 0);
>
> Isn't this going to trigger an abort on OSes that don't implement
> xengnttab_grant_copy? AFAICT the 'unimplemented' handler in libgnttab for
> this is just an abort.
So is the xengnttab_map_grant_refs and the pointer to
blkdev->xendev.gnttabdev would be invalid so the sring would not be
initialized a few lines earlier in that function leading to the fail of
the initialization. In case the gntdev does not implement the ioctl then
only an error code will be returned.
Paulina
>
> Roger.
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-07-19 10:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 8:38 [PATCH v3 0/2] qemu-qdisk: Implementation of grant copy operation Paulina Szubarczyk
2016-06-22 8:38 ` [PATCH v3 1/2] Interface for grant copy operation in libs Paulina Szubarczyk
2016-06-22 9:37 ` David Vrabel
2016-06-22 9:53 ` Paulina Szubarczyk
2016-06-22 11:24 ` Wei Liu
2016-06-22 14:19 ` Paulina Szubarczyk
2016-06-22 11:21 ` Wei Liu
2016-06-22 12:37 ` David Vrabel
2016-06-22 13:29 ` Wei Liu
2016-06-22 13:52 ` David Vrabel
2016-06-22 14:52 ` Wei Liu
2016-06-22 16:49 ` Wei Liu
2016-07-06 15:49 ` Roger Pau Monné
2016-07-05 16:27 ` George Dunlap
2016-07-08 13:18 ` Wei Liu
2016-07-13 9:12 ` Wei Liu
2016-06-22 8:38 ` [PATCH v3 2/2] qdisk - hw/block/xen_disk: grant copy implementation Paulina Szubarczyk
2016-07-13 12:34 ` Paulina Szubarczyk
2016-07-14 10:37 ` Wei Liu
2016-07-15 10:28 ` Paulina Szubarczyk
2016-07-15 11:15 ` Wei Liu
2016-07-15 17:11 ` Anthony PERARD
2016-07-19 10:16 ` Paulina Szubarczyk
2016-07-15 16:55 ` Anthony PERARD
2016-07-19 10:51 ` Paulina Szubarczyk
2016-07-19 9:12 ` Roger Pau Monné
2016-07-19 10:12 ` Paulina Szubarczyk [this message]
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=578DFD06.9000507@gmail.com \
--to=paulinaszubarczyk@gmail.com \
--cc=anthony.perard@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--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).