All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoder Stuart-B08248 <B08248@freescale.com>
To: Wood Scott-B07421 <B07421@freescale.com>,
	Tabi Timur-B04825 <B04825@freescale.com>
Cc: Gala Kumar-B11780 <B11780@freescale.com>,
	Alexander Graf <agraf@suse.de>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: RE: RFC: top level compatibles for virtual platforms
Date: Mon, 11 Jul 2011 17:41:20 +0000	[thread overview]
Message-ID: <9F6FE96B71CF29479FF1CDC8046E150316FBA5@039-SN1MPN1-003.039d.mgd.msft.net> (raw)
In-Reply-To: <20110711112418.4db9f41e@schlenkerla.am.freescale.net>



> -----Original Message-----
> From: Wood Scott-B07421
> Sent: Monday, July 11, 2011 11:24 AM
> To: Tabi Timur-B04825
> Cc: Yoder Stuart-B08248; Grant Likely; Benjamin Herrenschmidt; Gala Kumar=
-B11780; Wood Scott-
> B07421; Alexander Graf; linuxppc-dev@ozlabs.org
> Subject: Re: RFC: top level compatibles for virtual platforms
>=20
> On Mon, 11 Jul 2011 10:45:47 -0500
> Timur Tabi <timur@freescale.com> wrote:
>=20
> > >> Also, if these are KVM creations, shouldn't there be a "kvm" in the
> > >> compatible string somewhere?
> > >
> > > There is nothing KVM specific about these platforms.  Any hypervisor
> > > could create a similar virtual machine.
> >
> > True, but I think we're on a slippery slope, here.  Virtualization
> > allows us to create "virtual platforms" that are not well defined.
> > Linux requires a unique compatible string for each platform.
>=20
> The device tree is supposed to describe the hardware (virtual or otherwis=
e), not just supply
> what Linux wants.  Perhaps there simply shouldn't be a toplevel compatibl=
e if there's nothing
> appropriate to describe there -- and fix whatever issues Linux has with t=
hat.

But there is a concept in Linux of a platform 'machine':

define_machine(p4080_ds) {
        .name                   =3D "P4080 DS",
        .probe                  =3D p4080_ds_probe,
        .setup_arch             =3D corenet_ds_setup_arch,
        .init_IRQ               =3D corenet_ds_pic_init,
#ifdef CONFIG_PCI
        .pcibios_fixup_bus      =3D fsl_pcibios_fixup_bus,
#endif
        .get_irq                =3D mpic_get_coreint_irq,
        .restart                =3D fsl_rstcr_restart,
        .calibrate_decr         =3D generic_calibrate_decr,
        .progress               =3D udbg_progress,
};

Right now p4080_ds_probe needs something to match on to determine
whether this is the machine type.   How would it work if=20
there was no top level compatible to match on?   Some=20
platforms (e.g. e500v2-type) need mpc85xx_ds_pic_init(),
others need corenet_ds_pic_init().  We need a way to
select the machine.

Stuart

  reply	other threads:[~2011-07-11 17:41 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 [this message]
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
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=9F6FE96B71CF29479FF1CDC8046E150316FBA5@039-SN1MPN1-003.039d.mgd.msft.net \
    --to=b08248@freescale.com \
    --cc=B04825@freescale.com \
    --cc=B07421@freescale.com \
    --cc=B11780@freescale.com \
    --cc=agraf@suse.de \
    --cc=linuxppc-dev@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.