public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	kvm-ppc-devel <kvm-ppc-devel@lists.sourceforge.net>,
	jyoung5@us.ibm.com, Avi Kivity <avi@qumranet.com>
Subject: Re: Top level kvm-userspace directory getting	crowded	...	need new dir	for qemu dependencies
Date: Wed, 27 Feb 2008 12:56:26 -0600	[thread overview]
Message-ID: <1204138586.2532.56.camel@basalt> (raw)
In-Reply-To: <4D4A90C0-9771-4A83-9E22-CA9D3177F30D@suse.de>

On Wed, 2008-02-27 at 17:48 +0100, Alexander Graf wrote:
> On Feb 27, 2008, at 5:34 PM, Avi Kivity wrote:
> 
> > Hollis Blanchard wrote:
> >> It is a centrally co-ordinated effort, but it is not a package a  
> >> distro
> >> would carry. It is code shared by anything that needs to load a  
> >> PowerPC
> >> Linux kernel, for example: the kernel bootwrapper (part of the Linux
> >> source tree), u-boot firmware, Xend, and now qemu.
> >>
> >> Accordingly, a libfdt.rpm simply doesn't make sense, and the code is
> >> intended to be copied into any codebase that needs it.
> >>
> >
> > A static library  + headers (i.e. libfdt-devel.rpm) could have been
> > used, though Linux avoids external dependencies.
> 
> Why don't you try to talk to the other possible users and create a  
> version of the library, that at least can be packaged, even though for  
> now KVM would be the only user? Maybe others (unlikely Linux, maybe  
> Xen, probably dtc) would like to have a central library for device  
> trees too.

I think it's obvious that Linux and uboot will never use this. Unless
someone steps up to continue PowerPC Xen development, neither will Xen.
So you've now narrowed down the use case to dtc (which is libfdt
upstream) and qemu.

Whose problem are you trying to solve? It doesn't seem to be one that
any existing users have. If you want to push it, you should probably
propose it on linuxppc-dev@ozlabs.org , which is where libfdt is
discussed.

I'm sure as hell not going to advocate creating a standalone library,
push it into every package that supports PowerPC, and then telling users
they must build on a supported version of a supported distribution.

-- 
Hollis Blanchard
IBM Linux Technology Center


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2008-02-27 18:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25  6:50 Top level kvm-userspace directory getting crowded ... need new dir for qemu dependencies Jerone Young
2008-02-25  9:00 ` Avi Kivity
2008-02-26 17:24   ` Jerone Young
2008-02-27 10:59     ` Avi Kivity
2008-02-27 16:29     ` Hollis Blanchard
2008-02-27 16:34       ` Avi Kivity
2008-02-27 16:48         ` Alexander Graf
2008-02-27 16:59           ` Avi Kivity
2008-02-27 17:07             ` Alexander Graf
2008-02-27 18:56           ` Hollis Blanchard [this message]
2008-02-27 19:18             ` Alexander Graf
2008-02-27 20:22               ` [kvm-ppc-devel] " Hollis Blanchard
2008-02-27 21:20                 ` Alexander Graf
2008-02-27 22:19                   ` Hollis Blanchard
2008-02-27 22:32                     ` Alexander Graf
2008-03-02 18:38                     ` Luca Barbato
2008-02-27 19:25             ` Avi Kivity
2008-02-27 19:57               ` [kvm-ppc-devel] " Hollis Blanchard
2008-02-28  8:16                 ` Avi Kivity
2008-02-28 20:28                   ` Jerone Young
2008-03-02 16:41                     ` Avi Kivity

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=1204138586.2532.56.camel@basalt \
    --to=hollisb@us.ibm.com \
    --cc=agraf@suse.de \
    --cc=avi@qumranet.com \
    --cc=jyoung5@us.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=kvm-ppc-devel@lists.sourceforge.net \
    /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