From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752328AbeCYWMr (ORCPT ); Sun, 25 Mar 2018 18:12:47 -0400 Received: from terminus.zytor.com ([198.137.202.136]:57867 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751091AbeCYWMa (ORCPT ); Sun, 25 Mar 2018 18:12:30 -0400 Subject: Re: [PATCH v3 2/2] x86, cpuid: allow cpuid_read() to schedule To: Eric Dumazet , Eric Dumazet , x86 Cc: lkml , Thomas Gleixner , Borislav Petkov , Ingo Molnar , Hugh Dickins References: <20180323215818.127774-1-edumazet@google.com> <20180323215818.127774-2-edumazet@google.com> <3622b64c-bae6-00db-6a61-3ccf760144aa@zytor.com> From: "H. Peter Anvin" Message-ID: Date: Sun, 25 Mar 2018 15:11:54 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/23/18 18:01, Eric Dumazet wrote: > > Indeed, assuming a daemon can have threads running on all cpus :/ > > Some environments like to partition cpus for different jobs/containers. > Then it doesn't need to run it on all cpus... just the one that that particular daemon is "responsible" for. -hpa