From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tabi Timur-B04825 <B04825@freescale.com>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
Wood Scott-B07421 <B07421@freescale.com>,
Gala Kumar-B11780 <B11780@freescale.com>,
"paulus@samba.org" <paulus@samba.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc/85xx: disable timebase synchronization under the hypervisor
Date: Wed, 15 Jun 2011 12:33:16 +1000 [thread overview]
Message-ID: <1308105196.2635.16.camel@pasglop> (raw)
In-Reply-To: <4DF814A3.7070209@freescale.com>
On Wed, 2011-06-15 at 02:10 +0000, Tabi Timur-B04825 wrote:
> Benjamin Herrenschmidt wrote:
> > We might want to generically have a CPU feature bit indicating we are
> > running in guest vs. HV mode. I know Paulus is planning to introduce one
> > so you may want to sync with him.
>
> Are you talking about CPU_FTR_HVMODE_206?
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.
next prev parent reply other threads:[~2011-06-15 2:33 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 [this message]
2011-06-22 11:44 ` Kumar Gala
2011-06-22 14:55 ` Timur Tabi
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=1308105196.2635.16.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=B04825@freescale.com \
--cc=B07421@freescale.com \
--cc=B11780@freescale.com \
--cc=B29882@freescale.com \
--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 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.