Re: [PATCH v2 10/43] KVM: arm64: Move vGIC v4 handling for WFI out arch callback hook
Marc Zyngier <[email protected]>
| Newsgroups | org.kernel.vger.kvm-ppc,dev.linux.lists.kvmarm,org.infradead.lists.kvm-riscv,org.infradead.lists.linux-arm-kernel,org.infradead.lists.linux-riscv,org.kernel.vger.kvm,org.kernel.vger.linux-kernel,org.kernel.vger.linux-mips |
|---|---|
| Message-ID | <[email protected]> |
On 2021-11-30 11:39, Paolo Bonzini wrote:
> On 10/26/21 18:12, Paolo Bonzini wrote:
>> On 26/10/21 17:41, Marc Zyngier wrote:
>>>> This needs a word on why kvm_psci_vcpu_suspend does not need the
>>>> hooks. Or it needs to be changed to also use kvm_vcpu_wfi in the
>>>> PSCI
>>>> code, I don't know.
>>>>
>>>> Marc, can you review and/or advise?
>>> I was looking at that over the weekend, and that's a pre-existing
>>> bug. I would have addressed it independently, but it looks like you
>>> already have queued the patch.
>>
>> I have "queued" it, but that's just my queue - it's not on kernel.org
>> and it's not going to be in 5.16, at least not in the first batch.
>>
>> There's plenty of time for me to rebase on top of a fix, if you want
>> to send the fix through your kvm-arm pull request. Just Cc me so that
>> I understand what's going on.
>
> Since a month has passed and I didn't see anything related in the
> KVM-ARM pull requests, I am going to queue this patch. Any conflicts
> can be resolved through a kvmarm->kvm merge of either a topic branch
> or a tag that is destined to 5.16.
Can you at least spell out *when* this will land?
There is, in general, a certain lack of clarity about what you are
queuing,
where you are queuing it, and what release it targets.
Thanks,
M.
--
Jazz is not dead. It just smells funny...