All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "paolo.valente@linaro.org" <paolo.valente@linaro.org>
Cc: "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
	"tj@kernel.org" <tj@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: [WIP PATCHSET 0/4] WIP branch for bfq-mq
Date: Fri, 24 Feb 2017 18:44:55 +0000	[thread overview]
Message-ID: <1487961857.2575.8.camel@sandisk.com> (raw)
In-Reply-To: <62F8F65E-A376-44EB-B53C-C2CFB8F8693F@linaro.org>

On Wed, 2017-02-22 at 22:29 +0100, Paolo Valente wrote:
> thanks for this second attempt of yours.  Although, unfortunately, not
> providing some clear indication of the exact cause of your hang (apart
> from a possible deadlock), your log helped me notice another bug.
>=20
> At any rate, as I have just written to Jens, I have pushed a new
> version of the branch [1] (not just added new commits, but also
> integrated some old commit with new changes, to make it more quickly).
> The branch now contains both a fix for the above bug, and, more
> importantly, a fix for the circular dependencies that were still
> lurking around.  Could you please test it?

Hello Paolo,

I have good news: the same test system boots normally with the same
kernel config I used during my previous tests and with the latest
bfq-mq code (commit a965d19585c0) merged with kernel v4.10.

Thanks,

Bart.=

WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "paolo.valente@linaro.org" <paolo.valente@linaro.org>
Cc: "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
	"tj@kernel.org" <tj@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: [WIP PATCHSET 0/4] WIP branch for bfq-mq
Date: Fri, 24 Feb 2017 18:44:55 +0000	[thread overview]
Message-ID: <1487961857.2575.8.camel@sandisk.com> (raw)
In-Reply-To: <62F8F65E-A376-44EB-B53C-C2CFB8F8693F@linaro.org>

On Wed, 2017-02-22 at 22:29 +0100, Paolo Valente wrote:
> thanks for this second attempt of yours.  Although, unfortunately, not
> providing some clear indication of the exact cause of your hang (apart
> from a possible deadlock), your log helped me notice another bug.
> 
> At any rate, as I have just written to Jens, I have pushed a new
> version of the branch [1] (not just added new commits, but also
> integrated some old commit with new changes, to make it more quickly).
> The branch now contains both a fix for the above bug, and, more
> importantly, a fix for the circular dependencies that were still
> lurking around.  Could you please test it?

Hello Paolo,

I have good news: the same test system boots normally with the same
kernel config I used during my previous tests and with the latest
bfq-mq code (commit a965d19585c0) merged with kernel v4.10.

Thanks,

Bart.

  reply	other threads:[~2017-02-24 18:44 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 17:24 [WIP PATCHSET 0/4] WIP branch for bfq-mq Paolo Valente
2017-02-07 17:24 ` [WIP PATCHSET 1/4] blk-mq: pass bio to blk_mq_sched_get_rq_priv Paolo Valente
2017-02-10 16:10   ` Jens Axboe
2017-02-07 17:24 ` [WIP PATCHSET 2/4] Move thinktime from bic to bfqq Paolo Valente
2017-02-07 17:24 ` [WIP PATCHSET 3/4] Embed bfq-ioc.c and add locking on request queue Paolo Valente
2017-02-07 17:24 ` [WIP PATCHSET 4/4] Modify interface and operation to comply with blk-mq-sched Paolo Valente
2017-02-10 16:08 ` [WIP PATCHSET 0/4] WIP branch for bfq-mq Bart Van Assche
2017-02-10 16:08   ` Bart Van Assche
2017-02-10 16:49   ` Paolo Valente
2017-02-10 16:49     ` Paolo Valente
2017-02-10 16:45 ` Bart Van Assche
2017-02-10 16:45   ` Bart Van Assche
2017-02-10 16:49   ` Paolo Valente
2017-02-10 16:49     ` Paolo Valente
2017-02-10 18:13     ` Bart Van Assche
2017-02-10 18:13       ` Bart Van Assche
2017-02-10 19:49       ` Paolo Valente
2017-02-10 19:49         ` Paolo Valente
2017-02-13 21:07         ` Paolo Valente
2017-02-13 21:07           ` Paolo Valente
2017-02-13 22:07           ` Bart Van Assche
2017-02-13 22:07             ` Bart Van Assche
2017-02-13 22:38             ` Bart Van Assche
2017-02-13 22:38               ` Bart Van Assche
2017-02-22 21:29               ` Paolo Valente
2017-02-22 21:29                 ` Paolo Valente
2017-02-24 18:44                 ` Bart Van Assche [this message]
2017-02-24 18:44                   ` Bart Van Assche
2017-02-25 17:45                   ` Paolo Valente
2017-02-25 17:45                     ` Paolo Valente
2017-02-10 18:34 ` Bart Van Assche
2017-02-10 18:34   ` Bart Van Assche
2017-02-10 19:33   ` Paolo Valente
2017-02-10 19:33     ` Paolo Valente
2017-02-13 21:09 ` Paolo Valente
2017-02-13 21:09   ` Paolo Valente
2017-02-13 22:29   ` Jens Axboe

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=1487961857.2575.8.camel@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=axboe@kernel.dk \
    --cc=broonie@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.valente@linaro.org \
    --cc=tj@kernel.org \
    --cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.