Re: (subset) [PATCH 0/5] hyper-v: Don't assume cpu_possible_mask is dense

2025-01-02 Thread Martin K. Petersen
On Wed, 02 Oct 2024 20:53:28 -0700, mhkelle...@gmail.com wrote: > Code specific to Hyper-V guests currently assumes the cpu_possible_mask > is "dense" -- i.e., all bit positions 0 thru (nr_cpu_ids - 1) are set, > with no "holes". Therefore, num_possible_cpus() is assumed to be equal > to nr_cpu_id

Re: [PATCH 0/5] hyper-v: Don't assume cpu_possible_mask is dense

2024-12-17 Thread Wei Liu
On Wed, Dec 11, 2024 at 12:14:50AM +, Wei Liu wrote: > On Tue, Dec 10, 2024 at 07:58:34PM +, Michael Kelley wrote: > > From: mhkelle...@gmail.com Sent: Wednesday, October > > 2, 2024 8:53 PM > > > > > > Code specific to Hyper-V guests currently assumes the cpu_possible_mask > > > is "den

Re: [PATCH 0/5] hyper-v: Don't assume cpu_possible_mask is dense

2024-12-10 Thread Wei Liu
On Tue, Dec 10, 2024 at 07:58:34PM +, Michael Kelley wrote: > From: mhkelle...@gmail.com Sent: Wednesday, October 2, > 2024 8:53 PM > > > > Code specific to Hyper-V guests currently assumes the cpu_possible_mask > > is "dense" -- i.e., all bit positions 0 thru (nr_cpu_ids - 1) are set, > > w

RE: [PATCH 0/5] hyper-v: Don't assume cpu_possible_mask is dense

2024-12-10 Thread Michael Kelley
From: mhkelle...@gmail.com Sent: Wednesday, October 2, 2024 8:53 PM > > Code specific to Hyper-V guests currently assumes the cpu_possible_mask > is "dense" -- i.e., all bit positions 0 thru (nr_cpu_ids - 1) are set, > with no "holes". Therefore, num_possible_cpus() is assumed to be equal > to n

RE: [PATCH 0/5] hyper-v: Don't assume cpu_possible_mask is dense

2024-10-04 Thread Michael Kelley
From: Jakub Kicinski Sent: Friday, October 4, 2024 4:26 PM > > On Fri, 04 Oct 2024 23:20:40 + patchwork-bot+netdev...@kernel.org > wrote: > > - [net-next,5/5] hv_netvsc: Don't assume cpu_possible_mask is dense > > > https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/

Re: [PATCH 0/5] hyper-v: Don't assume cpu_possible_mask is dense

2024-10-04 Thread Jakub Kicinski
On Fri, 04 Oct 2024 23:20:40 + patchwork-bot+netdev...@kernel.org wrote: > - [net-next,5/5] hv_netvsc: Don't assume cpu_possible_mask is dense > https://git.kernel.org/netdev/net-next/c/c86ab60b92d1 On reflection I probably should have asked you for a fixes tag and applied it to net :S

Re: [PATCH 0/5] hyper-v: Don't assume cpu_possible_mask is dense

2024-10-04 Thread patchwork-bot+netdevbpf
Hello: This series was applied to netdev/net-next.git (main) by Jakub Kicinski : On Wed, 2 Oct 2024 20:53:28 -0700 you wrote: > From: Michael Kelley > > Code specific to Hyper-V guests currently assumes the cpu_possible_mask > is "dense" -- i.e., all bit positions 0 thru (nr_cpu_ids - 1) are s

Re: [PATCH 0/5] hyper-v: Don't assume cpu_possible_mask is dense

2024-10-04 Thread Peter Zijlstra
On Wed, Oct 02, 2024 at 08:53:28PM -0700, mhkelle...@gmail.com wrote: > > Michael Kelley (5): > x86/hyperv: Don't assume cpu_possible_mask is dense > Drivers: hv: Don't assume cpu_possible_mask is dense > iommu/hyper-v: Don't assume cpu_possible_mask is dense > scsi: storvsc: Don't assume

[PATCH 0/5] hyper-v: Don't assume cpu_possible_mask is dense

2024-10-02 Thread mhkelley58
From: Michael Kelley Code specific to Hyper-V guests currently assumes the cpu_possible_mask is "dense" -- i.e., all bit positions 0 thru (nr_cpu_ids - 1) are set, with no "holes". Therefore, num_possible_cpus() is assumed to be equal to nr_cpu_ids. Per a separate discussion[1], this assumption