From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: [PATCH] xen-blkfront: check feature-persitent on resume
Date: Fri, 23 May 2014 20:08:36 +0200 [thread overview]
Message-ID: <537F8EA4.2050506@citrix.com> (raw)
In-Reply-To: <20140523175105.GA8995@phenom.dumpdata.com>
On 23/05/14 19:51, Konrad Rzeszutek Wilk wrote:
> On Thu, May 22, 2014 at 04:40:07PM +0200, Roger Pau Monne wrote:
>> We are missing a check to see if the backend supports persistent
>> grants on resume, meaning we will always run with the value fetched
>> from the firsts host on which we run on.
>>
>> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
>> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>> Cc: David Vrabel <david.vrabel@citrix.com>
>> ---
>> drivers/block/xen-blkfront.c | 23 ++++++++++++++++-------
>> 1 files changed, 16 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
>> index efe1b47..00ae36b 100644
>> --- a/drivers/block/xen-blkfront.c
>> +++ b/drivers/block/xen-blkfront.c
>> @@ -1430,6 +1430,20 @@ static void split_bio_end(struct bio *bio, int error)
>> bio_put(bio);
>> }
>>
>> +static void blkfront_setup_persistent(struct blkfront_info *info)
>> +{
>> + unsigned int persistent;
>> + int err;
>> +
>> + err = xenbus_gather(XBT_NIL, info->xbdev->otherend,
>> + "feature-persistent", "%u", &persistent,
>> + NULL);
>> + if (err)
>> + info->feature_persistent = 0;
>> + else
>> + info->feature_persistent = persistent;
>> +}
>> +
>> static int blkif_recover(struct blkfront_info *info)
>> {
>> int i;
>> @@ -1456,6 +1470,7 @@ static int blkif_recover(struct blkfront_info *info)
>> info->shadow_free = info->ring.req_prod_pvt;
>> info->shadow[BLK_RING_SIZE-1].req.u.rw.id = 0x0fffffff;
>>
>> + blkfront_setup_persistent(info);
>> rc = blkfront_setup_indirect(info);
>> if (rc) {
>> kfree(copy);
>> @@ -1851,13 +1866,7 @@ static void blkfront_connect(struct blkfront_info *info)
>> if (!err && discard)
>> blkfront_setup_discard(info);
>>
>> - err = xenbus_gather(XBT_NIL, info->xbdev->otherend,
>> - "feature-persistent", "%u", &persistent,
>> - NULL);
>> - if (err)
>> - info->feature_persistent = 0;
>> - else
>> - info->feature_persistent = persistent;
>> + blkfront_setup_persistent(info);
>
> Should we also flush the ones that are on the info->grants list if
> we turning it off?
This path is only taken on the first connection, further calls to
blkfront_connect from resume code don't get here, because they take the
BLKIF_STATE_SUSPENDED path and just call blkif_recover and return. And
on disconnection blkfront_connect doesn't even get called.
Roger.
next prev parent reply other threads:[~2014-05-23 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 14:40 [PATCH] xen-blkfront: check feature-persitent on resume Roger Pau Monne
2014-05-23 17:51 ` Konrad Rzeszutek Wilk
2014-05-23 18:08 ` Roger Pau Monné [this message]
2014-06-13 15:37 ` [Xen-devel] " Roger Pau Monné
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=537F8EA4.2050506@citrix.com \
--to=roger.pau@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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