From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: "<kvm-ppc@vger.kernel.org>" <kvm-ppc@vger.kernel.org>,
"<kvm@vger.kernel.org>" <kvm@vger.kernel.org>,
"<linuxppc-dev@lists.ozlabs.org>" <linuxppc-dev@lists.ozlabs.org>,
Stuart Yoder <B08248@freescale.com>
Subject: Re: [PATCH] KVM: PPC: Don't sync timebase when inside KVM
Date: Wed, 29 Feb 2012 19:06:05 +0000 [thread overview]
Message-ID: <4F4E771D.1040403@freescale.com> (raw)
In-Reply-To: <39AA9511-4D56-4087-BC98-4BB32EF048AA@suse.de>
On 02/29/2012 12:28 PM, Alexander Graf wrote:
>
>
> On 29.02.2012, at 18:50, Scott Wood <scottwood@freescale.com> wrote:
>
>> On 02/28/2012 08:16 PM, Alexander Graf wrote:
>>> When we know that we're running inside of a KVM guest, we don't have to
>>> worry about synchronizing timebases between different CPUs, since the
>>> host already took care of that.
>>>
>>> This fixes CPU overcommit scenarios where vCPUs could hang forever trying
>>> to sync each other while not being scheduled.
>>>
>>> Reported-by: Stuart Yoder <B08248@freescale.com>
>>> Signed-off-by: Alexander Graf <agraf@suse.de>
>>
>> This should apply to any hypervisor, not just KVM.
>
> Sure, but do you have a generic function to evaluate that? :)
The presence of a hypervisor node without testing compatible. Might not
get them all, but at least it will cover more than just KVM.
>> Which platforms are you seeing this on? If it's on Freescale chips,
>> U-Boot should be doing the sync and Linux should never do it, even in
>> the absence of a hypervisor.
>
> This is on e500mc.
On e500mc Linux should never by trying to sync the timebase. If it is,
let's fix that.
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: "<linuxppc-dev@lists.ozlabs.org>" <linuxppc-dev@lists.ozlabs.org>,
"<kvm@vger.kernel.org>" <kvm@vger.kernel.org>,
"<kvm-ppc@vger.kernel.org>" <kvm-ppc@vger.kernel.org>
Subject: Re: [PATCH] KVM: PPC: Don't sync timebase when inside KVM
Date: Wed, 29 Feb 2012 13:06:05 -0600 [thread overview]
Message-ID: <4F4E771D.1040403@freescale.com> (raw)
In-Reply-To: <39AA9511-4D56-4087-BC98-4BB32EF048AA@suse.de>
On 02/29/2012 12:28 PM, Alexander Graf wrote:
>
>
> On 29.02.2012, at 18:50, Scott Wood <scottwood@freescale.com> wrote:
>
>> On 02/28/2012 08:16 PM, Alexander Graf wrote:
>>> When we know that we're running inside of a KVM guest, we don't have to
>>> worry about synchronizing timebases between different CPUs, since the
>>> host already took care of that.
>>>
>>> This fixes CPU overcommit scenarios where vCPUs could hang forever trying
>>> to sync each other while not being scheduled.
>>>
>>> Reported-by: Stuart Yoder <B08248@freescale.com>
>>> Signed-off-by: Alexander Graf <agraf@suse.de>
>>
>> This should apply to any hypervisor, not just KVM.
>
> Sure, but do you have a generic function to evaluate that? :)
The presence of a hypervisor node without testing compatible. Might not
get them all, but at least it will cover more than just KVM.
>> Which platforms are you seeing this on? If it's on Freescale chips,
>> U-Boot should be doing the sync and Linux should never do it, even in
>> the absence of a hypervisor.
>
> This is on e500mc.
On e500mc Linux should never by trying to sync the timebase. If it is,
let's fix that.
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: "<kvm-ppc@vger.kernel.org>" <kvm-ppc@vger.kernel.org>,
"<kvm@vger.kernel.org>" <kvm@vger.kernel.org>,
"<linuxppc-dev@lists.ozlabs.org>" <linuxppc-dev@lists.ozlabs.org>,
Stuart Yoder <B08248@freescale.com>
Subject: Re: [PATCH] KVM: PPC: Don't sync timebase when inside KVM
Date: Wed, 29 Feb 2012 13:06:05 -0600 [thread overview]
Message-ID: <4F4E771D.1040403@freescale.com> (raw)
In-Reply-To: <39AA9511-4D56-4087-BC98-4BB32EF048AA@suse.de>
On 02/29/2012 12:28 PM, Alexander Graf wrote:
>
>
> On 29.02.2012, at 18:50, Scott Wood <scottwood@freescale.com> wrote:
>
>> On 02/28/2012 08:16 PM, Alexander Graf wrote:
>>> When we know that we're running inside of a KVM guest, we don't have to
>>> worry about synchronizing timebases between different CPUs, since the
>>> host already took care of that.
>>>
>>> This fixes CPU overcommit scenarios where vCPUs could hang forever trying
>>> to sync each other while not being scheduled.
>>>
>>> Reported-by: Stuart Yoder <B08248@freescale.com>
>>> Signed-off-by: Alexander Graf <agraf@suse.de>
>>
>> This should apply to any hypervisor, not just KVM.
>
> Sure, but do you have a generic function to evaluate that? :)
The presence of a hypervisor node without testing compatible. Might not
get them all, but at least it will cover more than just KVM.
>> Which platforms are you seeing this on? If it's on Freescale chips,
>> U-Boot should be doing the sync and Linux should never do it, even in
>> the absence of a hypervisor.
>
> This is on e500mc.
On e500mc Linux should never by trying to sync the timebase. If it is,
let's fix that.
-Scott
next prev parent reply other threads:[~2012-02-29 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 2:16 [PATCH] KVM: PPC: Don't sync timebase when inside KVM Alexander Graf
2012-02-29 2:16 ` Alexander Graf
2012-02-29 2:16 ` Alexander Graf
2012-02-29 17:50 ` Scott Wood
2012-02-29 17:50 ` Scott Wood
2012-02-29 17:50 ` Scott Wood
2012-02-29 18:28 ` Alexander Graf
2012-02-29 18:28 ` Alexander Graf
2012-02-29 18:28 ` Alexander Graf
2012-02-29 19:06 ` Scott Wood [this message]
2012-02-29 19:06 ` Scott Wood
2012-02-29 19:06 ` Scott Wood
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=4F4E771D.1040403@freescale.com \
--to=scottwood@freescale.com \
--cc=B08248@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.