linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
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: Wed, 22 Jun 2011 09:55:36 -0500	[thread overview]
Message-ID: <4E020268.2020809@freescale.com> (raw)
In-Reply-To: <083792FF-81CD-407C-B6B8-6D0481A0D65D@kernel.crashing.org>

Kumar Gala wrote:
>> > 
>> > Well, not exactly. Paul wants to break that up since we're adding some
>> > 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.
>> > 
>> > Cheers,
>> > Ben.

> 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.

Just FYI, this particular patch is because of a limitation in the Freescale
hypervisor.  It's not because we're running in guest mode.  If the hypervisor
provided full emulation of the timebase register, then we wouldn't need this
patch.  The same can be said of KVM or any other hypervisor.

So a generic HV mode bit is not going to help me, unless there's also a bit
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 future
version adds timebase support.  We currently use the device tree for all this,
so I'm not sure what a FTR bit will gain us.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2011-06-22 14:56 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 [this message]
2011-06-23 17:22                 ` Scott Wood
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=4E020268.2020809@freescale.com \
    --to=timur@freescale.com \
    --cc=B07421@freescale.com \
    --cc=B11780@freescale.com \
    --cc=B29882@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 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).