All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
	Alexander Graf <agraf@suse.de>,
	Gala Kumar-B11780 <B11780@freescale.com>
Subject: Re: RFC: top level compatibles for virtual platforms
Date: Mon, 11 Jul 2011 12:54:23 -0500	[thread overview]
Message-ID: <4E1B38CF.2050408@freescale.com> (raw)
In-Reply-To: <20110711112418.4db9f41e@schlenkerla.am.freescale.net>

Scott Wood wrote:
> The device tree is supposed to describe the hardware (virtual or
> otherwise), not just supply what Linux wants.  Perhaps there simply
> shouldn't be a toplevel compatible if there's nothing appropriate to
> describe there -- and fix whatever issues Linux has with that.

That might be the way to go.  I wonder if we can get rid of the platform file
altogether, at least in some situations.

> But what about this is specific to kvm (the actual hypervisor info is
> already described in /hypervisor)?  Then we'll have to add a platform match
> for every other hypervisor out there that does the same thing.

I don't know enough about KVM to answer that question.

Frankly, I like the approach that Topaz takes -- add a "-hv" to the real
hardware platform.  The only drawback is that each platform needs to add support
for virtualization, but we already have this problem with Topaz today.

-- 
Timur Tabi
Linux kernel developer at Freescale

  parent reply	other threads:[~2011-07-11 17:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 18:43 RFC: top level compatibles for virtual platforms Yoder Stuart-B08248
2011-07-09  1:39 ` Tabi Timur-B04825
2011-07-09  2:42   ` Grant Likely
2011-07-11 14:36     ` Yoder Stuart-B08248
2011-07-11 14:34   ` Yoder Stuart-B08248
2011-07-11 15:45     ` Timur Tabi
2011-07-11 16:24       ` Scott Wood
2011-07-11 17:41         ` Yoder Stuart-B08248
2011-07-11 18:04           ` Scott Wood
2011-07-11 20:41             ` Yoder Stuart-B08248
2011-07-11 21:06               ` Scott Wood
2011-07-12 14:20                 ` Yoder Stuart-B08248
2011-07-11 17:54         ` Timur Tabi [this message]
2011-07-11 19:59     ` Grant Likely
2011-07-11 20: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=4E1B38CF.2050408@freescale.com \
    --to=timur@freescale.com \
    --cc=B07421@freescale.com \
    --cc=B11780@freescale.com \
    --cc=agraf@suse.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@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 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.