From: Shannon Zhao <shannon.zhao@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, christoffer.dall@linaro.org
Subject: Re: [PATCH for 3.14.y stable 18/22] arm/arm64: KVM: Require in-kernel vgic for the arch timers
Date: Thu, 02 Jul 2015 12:06:13 +0800 [thread overview]
Message-ID: <5594B8B5.1040103@linaro.org> (raw)
In-Reply-To: <20150701183647.GA1873@kroah.com>
On 2015/7/2 2:36, Greg KH wrote:
> On Tue, Jun 30, 2015 at 06:49:06PM +0800, shannon.zhao@linaro.org wrote:
>> From: Christoffer Dall <christoffer.dall@linaro.org>
>>
>> commit 05971120fca43e0357789a14b3386bb56eef2201 upstream.
>>
>> It is curently possible to run a VM with architected timers support
>> without creating an in-kernel VGIC, which will result in interrupts from
>> the virtual timer going nowhere.
>>
>> To address this issue, move the architected timers initialization to the
>> time when we run a VCPU for the first time, and then only initialize
>> (and enable) the architected timers if we have a properly created and
>> initialized in-kernel VGIC.
>>
>> When injecting interrupts from the virtual timer to the vgic, the
>> current setup should ensure that this never calls an on-demand init of
>> the VGIC, which is the only call path that could return an error from
>> kvm_vgic_inject_irq(), so capture the return value and raise a warning
>> if there's an error there.
>>
>> We also change the kvm_timer_init() function from returning an int to be
>> a void function, since the function always succeeds.
>>
>> Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
>> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
>> Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
>
> {sigh}
>
> You modified this patch and didn't say you modified it, despite me
> asking you to do so.
I don't think so. If you really have a look at this patch, you should
recognize that this patch is doing the same thing as the original patch
does.
> Why should I trust that the other patches you sent
Trust? Don't say that please. I never felt your trust even from the
beginning of this backport.
> weren't also modified?
>
> Ugh. I've stopped here in the series, and I'm really annoyed at this
> whole series and just how long it's taken to get this right for a
> feature that almost no one cares about...
>
> greg k-h
>
--
Shannon
next prev parent reply other threads:[~2015-07-02 4:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 10:48 [PATCH for 3.14.y stable 00/22] Backport fixes of KVM/ARM to 3.14.y stable kernel shannon.zhao
2015-06-30 10:48 ` [PATCH for 3.14.y stable 01/22] ARM/arm64: KVM: fix use of WnR bit in kvm_is_write_fault() shannon.zhao
2015-06-30 10:48 ` [PATCH for 3.14.y stable 02/22] KVM: ARM: vgic: plug irq injection race shannon.zhao
2015-06-30 10:48 ` [PATCH for 3.14.y stable 03/22] arm/arm64: KVM: Fix set_clear_sgi_pend_reg offset shannon.zhao
2015-06-30 10:48 ` [PATCH for 3.14.y stable 04/22] arm/arm64: KVM: Fix VTTBR_BADDR_MASK and pgd alloc shannon.zhao
2015-06-30 10:48 ` [PATCH for 3.14.y stable 05/22] arm: kvm: fix CPU hotplug shannon.zhao
2015-06-30 10:48 ` [PATCH for 3.14.y stable 06/22] arm/arm64: KVM: fix potential NULL dereference in user_mem_abort() shannon.zhao
2015-06-30 10:48 ` [PATCH for 3.14.y stable 07/22] arm/arm64: KVM: Ensure memslots are within KVM_PHYS_SIZE shannon.zhao
2015-06-30 10:48 ` [PATCH for 3.14.y stable 08/22] arm: kvm: STRICT_MM_TYPECHECKS fix for user_mem_abort shannon.zhao
2015-06-30 10:48 ` [PATCH for 3.14.y stable 09/22] arm64: KVM: fix unmapping with 48-bit VAs shannon.zhao
2015-06-30 10:48 ` [PATCH for 3.14.y stable 10/22] arm/arm64: KVM: vgic: Fix error code in kvm_vgic_create() shannon.zhao
2015-06-30 10:48 ` [PATCH for 3.14.y stable 11/22] arm64/kvm: Fix assembler compatibility of macros shannon.zhao
2015-06-30 10:49 ` [PATCH for 3.14.y stable 12/22] arm/arm64: kvm: drop inappropriate use of kvm_is_mmio_pfn() shannon.zhao
2015-06-30 10:49 ` [PATCH for 3.14.y stable 13/22] arm/arm64: KVM: Don't clear the VCPU_POWER_OFF flag shannon.zhao
2015-06-30 10:49 ` [PATCH for 3.14.y stable 14/22] arm/arm64: KVM: Correct KVM_ARM_VCPU_INIT power off option shannon.zhao
2015-06-30 10:49 ` [PATCH for 3.14.y stable 15/22] arm/arm64: KVM: Reset the HCR on each vcpu when resetting the vcpu shannon.zhao
2015-06-30 10:49 ` [PATCH for 3.14.y stable 16/22] arm/arm64: KVM: Introduce stage2_unmap_vm shannon.zhao
2015-06-30 10:49 ` [PATCH for 3.14.y stable 17/22] arm/arm64: KVM: Don't allow creating VCPUs after vgic_initialized shannon.zhao
2015-06-30 10:49 ` [PATCH for 3.14.y stable 18/22] arm/arm64: KVM: Require in-kernel vgic for the arch timers shannon.zhao
2015-07-01 18:36 ` Greg KH
2015-07-02 4:06 ` Shannon Zhao [this message]
2015-07-02 4:30 ` Greg KH
2015-06-30 10:49 ` [PATCH for 3.14.y stable 19/22] arm64: KVM: Fix TLB invalidation by IPA/VMID shannon.zhao
2015-06-30 10:49 ` [PATCH for 3.14.y stable 20/22] arm64: KVM: Fix HCR setting for 32bit guests shannon.zhao
2015-06-30 10:49 ` [PATCH for 3.14.y stable 21/22] arm64: KVM: Do not use pgd_index to index stage-2 pgd shannon.zhao
2015-06-30 10:49 ` [PATCH for 3.14.y stable 22/22] arm/arm64: KVM: Keep elrsr/aisr in sync with software model shannon.zhao
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=5594B8B5.1040103@linaro.org \
--to=shannon.zhao@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.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.