linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Bob Liu <bob.liu@oracle.com>, <xen-devel@lists.xen.org>
Cc: <david.vrabel@citrix.com>, <justing@spectralogic.com>,
	<konrad.wilk@oracle.com>, <paul.durrant@citrix.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] driver: xen-blkfront: move talk_to_blkback to a more suitable place
Date: Thu, 21 May 2015 12:52:13 +0200	[thread overview]
Message-ID: <555DB8DD.2080000@citrix.com> (raw)
In-Reply-To: <1432127422-6797-1-git-send-email-bob.liu@oracle.com>

El 20/05/15 a les 15.10, Bob Liu ha escrit:
> The major responsibility of talk_to_blkback() is allocate and initialize the
> request ring and writes the ring info stuff out.
                   ^ write             ^ to xenstore.
> But this work should be done after backend entered 'XenbusStateInitWait' as
> defined in the protocol file.
> See xen/include/public/io/blkif.h in XEN git tree:
> Front                                Back
> =================================    =====================================
> XenbusStateInitialising              XenbusStateInitialising
>  o Query virtual device               o Query backend device identification
>    properties.                          data.
>  o Setup OS device instance.          o Open and validate backend device.
>                                       o Publish backend features and
>                                         transport parameters.
>                                                      |
>                                                      |
>                                                      V
>                                      XenbusStateInitWait
> 
> o Query backend features and
>   transport parameters.
> o Allocate and initialize the
>   request ring.
> 
> There is no problem with this yet, but it is an violation of the design and
> furthermore it would not allow frontend/backend to negotiate 'multi-page' and
> 'multi-queue' features.
> 
> Changes in v2:
>  - Re-write the commit message to be more clear.
> 
> Signed-off-by: Bob Liu <bob.liu@oracle.com>

With that fixed:

Acked-by: Roger Pau Monné <roger.pau@citrix.com>

Roger.


  parent reply	other threads:[~2015-05-21 10:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 13:10 [PATCH v2 1/2] driver: xen-blkfront: move talk_to_blkback to a more suitable place Bob Liu
2015-05-20 13:10 ` [PATCH v4 2/2] xen/block: add multi-page ring support Bob Liu
2015-05-20 13:21   ` [Xen-devel] " Julien Grall
2015-05-20 14:56     ` Roger Pau Monné
2015-05-20 15:00       ` Julien Grall
2015-05-20 23:47         ` Bob Liu
2015-05-21 11:22   ` Roger Pau Monné
2015-05-21 13:03     ` Bob Liu
2015-05-21 13:33       ` Roger Pau Monné
2015-05-21 10:52 ` Roger Pau Monné [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-21 23:59 [PATCH v2 1/2] driver: xen-blkfront: move talk_to_blkback to a more suitable place Bob Liu

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=555DB8DD.2080000@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=bob.liu@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=justing@spectralogic.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.durrant@citrix.com \
    --cc=xen-devel@lists.xen.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).