From owner-freebsd-current@freebsd.org  Mon Jan 23 07:58:04 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5BFCBCBC50F
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 23 Jan 2017 07:58:04 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [88.99.82.50])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 21FB8E48;
 Mon, 23 Jan 2017 07:58:03 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from hps2016.home.selasky.org (unknown [62.141.129.119])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id E57AF1FE100;
 Mon, 23 Jan 2017 08:57:34 +0100 (CET)
Subject: Re: Strange issue after early AP startup
To: Jia-Shiun Li <jiashiun@gmail.com>
References: <b9c53237-4b1a-a140-f692-bf5837060b18@selasky.org>
 <1484682389.86335.166.camel@freebsd.org>
 <11f27a15-f9bc-8988-a17e-78aeff1745fb@selasky.org>
 <3558195.Ack1AKBXSB@ralph.baldwin.cx>
 <24593c49-b0d5-8aaf-e11b-bfef4704267e@selasky.org>
 <f675e822-afce-b666-72ca-9a6ea77209e5@selasky.org>
 <CAHNYxxPqcuk9axdwxnCOHO16Rve5NmPqq5xcnyfGeLJJK+Cw5A@mail.gmail.com>
 <3b32cebd-6b8c-421c-314f-6e40dc50d03c@selasky.org>
 <CAHNYxxNTWC_iD+vaUnOt_d8r=GKRDKQwc0ozsF+2dpq6ZXc4SQ@mail.gmail.com>
Cc: John Baldwin <jhb@freebsd.org>, Ian Lepore <ian@freebsd.org>,
 FreeBSD Current <freebsd-current@freebsd.org>,
 Konstantin Belousov <kib@freebsd.org>, Bruce Evans <brde@optusnet.com.au>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <5cb7b677-a4d9-0589-82e9-be8671fe7977@selasky.org>
Date: Mon, 23 Jan 2017 08:57:25 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CAHNYxxNTWC_iD+vaUnOt_d8r=GKRDKQwc0ozsF+2dpq6ZXc4SQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jan 2017 07:58:04 -0000

On 01/23/17 06:27, Jia-Shiun Li wrote:
> On Sat, Jan 21, 2017 at 3:51 PM, Hans Petter Selasky <hps@selasky.org>
> wrote:
>
>> FYI:
>>
>> https://svnweb.freebsd.org/changeset/base/312551
>>
>>
> Hi hps,
>
> sorry I have to correct my test results.
> I found that I did not revert changes to kernel config,
> which commented out EARLY_AP_STARTUP option,
> before testing you patches. So they were tested without
> EARLY_AP_STARTUP.
>
> I tested again your patches with kernel config reverted,
> and they (and head as of r312620) did not solve the c2d
> system time lag issue.
>
> vmstat results attached.
> And also my apology for this stupid mistake.
>

This might be another issue, not related to my patch.

--HPS