On 5/6/2025 11:23 PM, Wei Liu wrote:
On Tue, May 06, 2025 at 02:58:34AM +, Wei Liu wrote:
On Wed, Apr 30, 2025 at 01:47:20PM -0700, Roman Kisel wrote:
When starting APs, confidential guests and paravisor guests
need to know the CPU number, and the pattern of using the linear
search has e
> On Wed, Apr 30, 2025 at 01:47:20PM -0700, Roman Kisel wrote:
> > When starting APs, confidential guests and paravisor guests need to
> > know the CPU number, and the pattern of using the linear search has
> > emerged in several places. With N processors that leads to the O(N^2)
> > time complexit
On Tue, May 06, 2025 at 02:58:34AM +, Wei Liu wrote:
> On Wed, Apr 30, 2025 at 01:47:20PM -0700, Roman Kisel wrote:
> > When starting APs, confidential guests and paravisor guests
> > need to know the CPU number, and the pattern of using the linear
> > search has emerged in several places. With
On Wed, Apr 30, 2025 at 01:47:20PM -0700, Roman Kisel wrote:
> When starting APs, confidential guests and paravisor guests
> need to know the CPU number, and the pattern of using the linear
> search has emerged in several places. With N processors that leads
> to the O(N^2) time complexity.
>
> Pr
On Mon, May 05, 2025 at 11:12:10AM -0700, Dave Hansen wrote:
> On 5/5/25 11:01, Wei Liu wrote:
> > You don't need to do that for this patch. Please point me to Thomas'
> > reply to the previous version and I can add the missing tag to patch
> > while I queue it.
>
> It's right here:
>
> htt
On Tue, May 06, 2025 at 02:52:54AM +, Wei Liu wrote:
> On Mon, May 05, 2025 at 11:12:10AM -0700, Dave Hansen wrote:
> > On 5/5/25 11:01, Wei Liu wrote:
> > > You don't need to do that for this patch. Please point me to Thomas'
> > > reply to the previous version and I can add the missing tag to
On 5/5/25 11:01, Wei Liu wrote:
> You don't need to do that for this patch. Please point me to Thomas'
> reply to the previous version and I can add the missing tag to patch
> while I queue it.
It's right here:
https://lore.kernel.org/all/8734dnouq6.ffs@tglx/
It's pretty darn trivial to
On Mon, May 05, 2025 at 10:22:47AM -0700, Roman Kisel wrote:
>
>
> On 5/2/2025 10:32 AM, Wei Liu wrote:
> > On Wed, Apr 30, 2025 at 01:47:20PM -0700, Roman Kisel wrote:
>
> [...]
>
> > > arch/x86/coco/sev/core.c | 13 ++---
> > > arch/x86/hyperv/hv_vtl.c | 12 ++--
On 5/2/2025 10:32 AM, Wei Liu wrote:
On Wed, Apr 30, 2025 at 01:47:20PM -0700, Roman Kisel wrote:
[...]
arch/x86/coco/sev/core.c | 13 ++---
arch/x86/hyperv/hv_vtl.c | 12 ++--
arch/x86/hyperv/ivm.c | 2 +-
arch/x86/include/asm/apic.h
On Wed, Apr 30, 2025 at 01:47:20PM -0700, Roman Kisel wrote:
> When starting APs, confidential guests and paravisor guests
> need to know the CPU number, and the pattern of using the linear
> search has emerged in several places. With N processors that leads
> to the O(N^2) time complexity.
>
> Pr
On Wed, Apr 30 2025 at 13:47, Roman Kisel wrote:
> When starting APs, confidential guests and paravisor guests
> need to know the CPU number, and the pattern of using the linear
> search has emerged in several places. With N processors that leads
> to the O(N^2) time complexity.
>
> Provide the CPU
From: Roman Kisel Sent: Wednesday, April 30, 2025
1:47 PM
>
> When starting APs, confidential guests and paravisor guests
> need to know the CPU number, and the pattern of using the linear
> search has emerged in several places. With N processors that leads
> to the O(N^2) time complexity.
>
>
When starting APs, confidential guests and paravisor guests
need to know the CPU number, and the pattern of using the linear
search has emerged in several places. With N processors that leads
to the O(N^2) time complexity.
Provide the CPU number in the AP wake up callback so that one can
get the C
13 matches
Mail list logo
