[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1487023626.2719.9.camel@sandisk.com>
Date: Mon, 13 Feb 2017 22:07:20 +0000
From: Bart Van Assche <Bart.VanAssche@...disk.com>
To: "paolo.valente@...aro.org" <paolo.valente@...aro.org>
CC: "ulf.hansson@...aro.org" <ulf.hansson@...aro.org>,
"tj@...nel.org" <tj@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"broonie@...nel.org" <broonie@...nel.org>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"axboe@...nel.dk" <axboe@...nel.dk>
Subject: Re: [WIP PATCHSET 0/4] WIP branch for bfq-mq
On Mon, 2017-02-13 at 22:07 +0100, Paolo Valente wrote:
> but what do you think about trying this fix?
Sorry but with ... the same server I used for the previous test still
didn't boot up properly. A screenshot is available at
https://goo.gl/photos/Za9QVGCNe2BJBwxVA.
> Otherwise, if you have no news or suggestions, would you be willing to
> try my micro-logging proposal https://github.com/Algodev-github/bfq-mq?
Sorry but it's not clear to me what logging mechanism you are referring
to and how to enable it? Are you perhaps referring to
CONFIG_BFQ_REDIRECT_TO_CONSOLE?
Thanks,
Bart.
Powered by blists - more mailing lists