From: Tim Chen <tim.c.chen@linux.intel.com>
To: Subhra Mazumdar <subhra.mazumdar@oracle.com>,
linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>
Subject: Re: Gang scheduling
Date: Wed, 13 Feb 2019 10:25:09 -0800 [thread overview]
Message-ID: <70d78b14-53a6-4523-856b-e67139a55a58@linux.intel.com> (raw)
In-Reply-To: <890bd498-93b2-5d9d-8066-21278540727f@oracle.com>
On 2/12/19 6:57 PM, Subhra Mazumdar wrote:
> Hi Tim,
>
> On 10/12/18 11:01 AM, Tim Chen wrote:
>> On 10/10/2018 05:09 PM, Subhra Mazumdar wrote:
>>> Hi,
>>>
>>> I was following the Coscheduling patch discussion on lkml and Peter mentioned he had a patch series. I found the following on github.
>>>
>>> https://github.com/pdxChen/gang/commits/sched_1.23-loadbal
>>>
>>> I would like to test this with KVMs. Are the commits from 38d5acb to f019876 sufficient? Also is there any documentaion on how to use it (any knobs I need to turn on for gang scheduling to happen?) or is it enabled by default for KVMs?
>>>
>>> Thanks,
>>> Subhra
>>>
>> I would suggest you try
>> https://github.com/pdxChen/gang/tree/sched_1.23-base
>> without the load balancing part of gang scheduling.
>> It is enabled by default for KVMs.
> I applied the following 3 patches on 4.19 and tried to install a KVM (with
> virt-install). But the kernel hangs with following error:
>
> kernel:watchdog: BUG: soft lockup - CPU#21 stuck for 23s! [kworker/21:1:573]
>
> kvm,sched: Track VCPU threads
> x86/kvm,sched: Add fast path for reschedule interrupt
> sched: Optimize scheduler_ipi()
>
> The track VCPU patch seems to be the culprit.
>
> Thanks,
> Subhra
Thanks for giving it a try. Peter is working on a new version. So I'll not try
to debug this patchset for now.
Tim
prev parent reply other threads:[~2019-02-13 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 0:09 Subhra Mazumdar
2018-10-12 18:01 ` Tim Chen
2018-10-15 22:49 ` Subhra Mazumdar
2019-02-13 2:57 ` Subhra Mazumdar
2019-02-13 18:25 ` Tim Chen [this message]
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=70d78b14-53a6-4523-856b-e67139a55a58@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=subhra.mazumdar@oracle.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
all inboxes | Powered by JetHome®