From: Rik van Riel <riel@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, tj@kernel.org,
umgwanakikbuti@gmail.com, lizefan@huawei.com
Subject: Re: [PATCH 1/2] show isolated cpus in sysfs
Date: Mon, 04 May 2015 17:15:52 -0400 [thread overview]
Message-ID: <5547E188.9090909@redhat.com> (raw)
In-Reply-To: <20150424214901.GB16861@kroah.com>
On 04/24/2015 05:49 PM, Greg KH wrote:
> On Fri, Apr 24, 2015 at 05:22:12PM -0400, Rik van Riel wrote:
>> On 04/24/2015 05:11 PM, Frederic Weisbecker wrote:
>>> On Fri, Apr 24, 2015 at 03:24:27PM -0400, riel@redhat.com wrote:
>>>> From: Rik van Riel <riel@redhat.com>
>>>>
>>>> After system bootup, there is no totally reliable way to see
>>>> which CPUs are isolated, because the kernel may modify the
>>>> CPUs specified on the isolcpus= kernel command line option.
>>>>
>>>> Export the CPU list that actually got isolated in sysfs,
>>>> specifically in the file /sys/devices/system/cpu/isolated
>>>>
>>>> This can be used by system management tools like libvirt,
>>>> openstack, and others to ensure proper placement of tasks.
>>>>
>>>> Suggested-by: Li Zefan <lizefan@huawei.com>
>>>> Signed-off-by: Rik van Riel <riel@redhat.com>
>>>
>>> This patch should go through Peterz.
>>
>> Oh, fun. That's what I get for getting the get_maintainer.pl
>> script, which told me to go through Greg KH instead :)
>>
>> $ ./scripts/get_maintainer.pl -f drivers/base/cpu.c
>> Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:DRIVER CORE,
>> KOBJ...)
>> linux-kernel@vger.kernel.org (open list)
>
> That's right, I can take this, I missed this the last time Rik sent
> these, that's my fault.
Ping?
Let me harass you before we both forget and this
thing falls through the cracks again :)
--
All rights reversed
next prev parent reply other threads:[~2015-05-04 21:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 19:24 [PATCH 0/2 resend] show isolated & nohz_full " riel
2015-04-24 19:24 ` [PATCH 1/2] show isolated " riel
2015-04-24 21:11 ` Frederic Weisbecker
2015-04-24 21:16 ` Tejun Heo
2015-04-24 21:22 ` Rik van Riel
2015-04-24 21:49 ` Greg KH
2015-05-04 21:15 ` Rik van Riel [this message]
2015-04-24 19:24 ` [PATCH 2/2] show nohz_full " riel
2015-04-28 19:18 ` Chris Metcalf
2015-04-25 5:29 ` [PATCH 0/2 resend] show isolated & " Mike Galbraith
-- strict thread matches above, loose matches on Subject: below --
2015-03-27 21:50 [PATCH 0/2] " riel
2015-03-27 21:50 ` [PATCH 1/2] show isolated " riel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5547E188.9090909@redhat.com \
--to=riel@redhat.com \
--cc=fweisbec@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
--cc=umgwanakikbuti@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome