From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <marc.zyngier@arm.com>
Received-SPF: Pass (sender SPF authorized) identity=mailfrom;
 client-ip=217.140.101.70; helo=foss.arm.com;
 envelope-from=marc.zyngier@arm.com; receiver=edk2-devel@lists.01.org 
Received: from foss.arm.com (usa-sjc-mx-foss1.foss.arm.com [217.140.101.70])
 by ml01.01.org (Postfix) with ESMTP id 0C193223FCF4C
 for <edk2-devel@lists.01.org>; Thu, 15 Mar 2018 02:34:20 -0700 (PDT)
Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249])
 by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 7C7F480D;
 Thu, 15 Mar 2018 02:40:43 -0700 (PDT)
Received: from [10.1.206.75] (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249])
 by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id
 8D3B63F24A; Thu, 15 Mar 2018 02:40:42 -0700 (PDT)
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>, Guo Heyi <heyi.guo@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
 Yi Li <phoenix.liyi@huawei.com>, Leif Lindholm <leif.lindholm@linaro.org>
References: <1520901090-96694-1-git-send-email-heyi.guo@linaro.org>
 <1520901090-96694-2-git-send-email-heyi.guo@linaro.org>
 <0403f2bf-d6a8-b101-73a2-949946f71e46@arm.com>
 <20180314002509.GE96299@SZX1000114654> <86a7vbaynt.wl-marc.zyngier@arm.com>
 <CAKv+Gu_y5wZqeja9Jaaj6dLN2X1x96CwigY6QTr466=41GKZYw@mail.gmail.com>
 <20180315071133.GD108227@SZX1000114654>
 <CAKv+Gu-JTy=gkcLGWW5P-8KJr092+ugOL12m+9s4Q+WaUW_1fQ@mail.gmail.com>
From: Marc Zyngier <marc.zyngier@arm.com>
Organization: ARM Ltd
Message-ID: <147790b3-379c-81b8-57e1-f7b5d99b9db7@arm.com>
Date: Thu, 15 Mar 2018 09:40:41 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAKv+Gu-JTy=gkcLGWW5P-8KJr092+ugOL12m+9s4Q+WaUW_1fQ@mail.gmail.com>
Subject: Re: [PATCH v2 1/1] ArmPkg/TimerDxe: Add ISB for timer compare value reload
X-BeenThere: edk2-devel@lists.01.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: EDK II Development  <edk2-devel.lists.01.org>
List-Unsubscribe: <https://lists.01.org/mailman/options/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=unsubscribe>
List-Archive: <http://lists.01.org/pipermail/edk2-devel/>
List-Post: <mailto:edk2-devel@lists.01.org>
List-Help: <mailto:edk2-devel-request@lists.01.org?subject=help>
List-Subscribe: <https://lists.01.org/mailman/listinfo/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2018 09:34:21 -0000
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 7bit

On 15/03/18 07:30, Ard Biesheuvel wrote:
> On 15 March 2018 at 07:11, Guo Heyi <heyi.guo@linaro.org> wrote:
>> Hi Marc and Ard,
>>
>> I found the timer re-enable code was added by Ard for special reason:
>>
>> commit b1a633434ddc5fc28de817debd963f7845fb78c7
>> Author: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> Date:   Thu Sep 18 21:16:47 2014 +0000
>>
>>     ArmPkg/TimerDxe: add workaround for KVM timer interrupt handling
>>
>> So this line of code cannot be removed and I will add an ISB after enabling
>> timer.
>>
> 
> I'm not sure. IIUC, the KVM issue that required this has been fixed
> long ago, and I don't want to carry this forever. Marc?

This has been fixed quite a while ago:

commit f120cd6533d21075ab103ae6c225b1697853660d
Author: Marc Zyngier <marc.zyngier@arm.com>
Date:   Mon Jun 23 13:59:13 2014 +0100

    KVM: arm/arm64: timer: Allow the timer to control the active state

    In order to remove the crude hack where we sneak the masked bit
    into the timer's control register, make use of the phys_irq_map
    API control the active state of the interrupt.

    This causes some limited changes to allow for potential error
    propagation.

    Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
    Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>

>> Another strange thing is that we got lots of "Spurious GIC interrupt" error
>> messages when timer enable code was removed, though at last it could boot to EFI
>> shell. Please let me know if you have any idea about the possible reason of this
>> issue.
>>
> 
> No idea, sorry.

Me neither. You'd have to dump the control register before and after,
and work out what is being changed exactly.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...