From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <timur@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"paulus@samba.org" <paulus@samba.org>,
McClintock Matthew-B29882 <B29882@freescale.com>,
Gala Kumar-B11780 <B11780@freescale.com>
Subject: Re: [PATCH] powerpc/85xx: disable timebase synchronization under the hypervisor
Date: Thu, 23 Jun 2011 12:22:10 -0500 [thread overview]
Message-ID: <20110623122210.06ee9f55@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <4E020268.2020809@freescale.com>
On Wed, 22 Jun 2011 09:55:36 -0500
Timur Tabi <timur@freescale.com> wrote:
> Kumar Gala wrote:
> >> >=20
> >> > Well, not exactly. Paul wants to break that up since we're adding so=
me
> >> > primitive support for 201 HV mode too (for 970's). Last we discussed,
> >> > the plan was to go for a generic HV mode bit and a separate bit for =
the
> >> > version.
> >> >=20
> >> > Cheers,
> >> > Ben.
>=20
> > Any ETA on Paul's intro of the FTR bit? If not I'll pull this into my =
'next' tree and we can clean up later.
>=20
> Just FYI, this particular patch is because of a limitation in the Freesca=
le
> hypervisor. It's not because we're running in guest mode. If the hyperv=
isor
> provided full emulation of the timebase register, then we wouldn't need t=
his
> patch. The same can be said of KVM or any other hypervisor.
=46rom Power ISA 2.06B, book III-E, section 9.2.1:
Virtualized Implementation Note:
In virtualized implementations, TBU and TBL are
read-only.
> So a generic HV mode bit is not going to help me, unless there's also a b=
it
> that's specific to our hypervisor. And even then, we would need some way=
to
> differentiate among different versions of our hypervisor, in case some fu=
ture
> version adds timebase support.=20
That's very unlikely to happen.
Ideally we would avoid doing this sync even when not running under a
hypervisor, as long as firmware has done the sync, and kexec hasn't messed
it up. Besides being a waste of boot time, the firmware's sync is
probably tighter since it can use a platform-specific mechanism to start all
the timebases at once.
-Scott
next prev parent reply other threads:[~2011-06-23 17:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 23:04 [PATCH] powerpc/85xx: disable timebase synchronization under the hypervisor Timur Tabi
2011-06-14 23:14 ` Scott Wood
2011-06-14 23:15 ` Timur Tabi
2011-06-14 23:25 ` Scott Wood
2011-06-15 1:58 ` Benjamin Herrenschmidt
2011-06-15 2:10 ` Tabi Timur-B04825
2011-06-15 2:33 ` Benjamin Herrenschmidt
2011-06-22 11:44 ` Kumar Gala
2011-06-22 14:55 ` Timur Tabi
2011-06-23 17:22 ` Scott Wood [this message]
2011-06-23 17:33 ` Timur Tabi
2011-06-23 17:48 ` Scott Wood
2011-06-24 2:36 ` Segher Boessenkool
2011-06-24 2:38 ` Tabi Timur-B04825
2011-06-24 3:50 ` Segher Boessenkool
2011-06-24 15:16 ` Scott Wood
2011-06-24 23:36 ` Benjamin Herrenschmidt
2011-06-27 13:35 ` Kumar Gala
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=20110623122210.06ee9f55@schlenkerla.am.freescale.net \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B11780@freescale.com \
--cc=B29882@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=timur@freescale.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;
as well as URLs for NNTP newsgroup(s).