Le 11/12/2023 à 03:50, Luming Yu a écrit :
> [Vous ne recevez pas souvent de courriers de luming...@shingroup.cn.
> Découvrez pourquoi ceci est important à
> https://aka.ms/LearnAboutSenderIdentification ]
>
> The support for user return notifier infrastructure
> is hooked into powerpc archite
On Fri, 8 Dec 2023 22:00:44 +0530
Naveen N Rao wrote:
> Rather than hard-coding the offset into a function to be used to
> determine if a kprobe is at function entry, use ftrace_location() to
> determine the ftrace location within the function and categorize all
> instructions till that offset t
On 12/11/23 9:26 AM, Vaibhav Jain wrote:
> Hi Aneesh,
>
> Thanks for looking into this patch. My responses inline:
>
> "Aneesh Kumar K.V (IBM)" writes:
>
>
>> May be we should use
>> firmware_has_feature(FW_FEATURE_H_COPY_TOFROM_GUEST))?
>>
>> the nestedv2 can end up using the above hcall if
Hi Aneesh,
Thanks for looking into this patch. My responses inline:
"Aneesh Kumar K.V (IBM)" writes:
> May be we should use
> firmware_has_feature(FW_FEATURE_H_COPY_TOFROM_GUEST))?
>
> the nestedv2 can end up using the above hcall if it is supported by the
> hypervisor right? In its absence we
* Srikar Dronamraju [2023-11-09 11:19:28]:
Hi Michael,
> PowerVM systems configured in shared processors mode have some unique
> challenges. Some device-tree properties will be missing on a shared
> processor. Hence some sched domains may not make sense for shared processor
> systems.
>
>
Did
On 11/30/23 18:35, Christophe Leroy wrote:
>
> Le 30/11/2023 à 03:53, Rohan McLure a écrit :
>> For 32-bit systems which have no usecases for p{m,u}d_pte() prior to
>> page table checking, implement default stubs.
> Is that the best solution ?
>
> If I understand correctly, it is only needed for
>
The support for user return notifier infrastructure
is hooked into powerpc architecture.
---
arch/powerpc/Kconfig| 1 +
arch/powerpc/include/asm/entry-common.h | 16
arch/powerpc/include/asm/thread_info.h | 2 ++
arch/powerpc/kernel/process.c | 2
On Thu, Dec 7, 2023 at 8:21 AM Sean Christopherson wrote:
> Doh. We got the less obvious cases and missed the obvious one.
>
> Ugh, and we also missed a related mess in kvm_guest_apic_has_interrupt().
> That
> thing should really be folded into vmx_has_nested_events().
>
> Good gravy. And vmx_
