public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	kvm-ppc-devel <kvm-ppc-devel@lists.sourceforge.net>
Subject: Re: [kvm-ppc-devel] Top level kvm-userspace directory	getting	crowded ...	need new dir	for qemu dependencies
Date: Wed, 27 Feb 2008 13:57:27 -0600	[thread overview]
Message-ID: <1204142247.2532.70.camel@basalt> (raw)
In-Reply-To: <47C5B941.2020509@qumranet.com>

On Wed, 2008-02-27 at 21:25 +0200, Avi Kivity wrote:
> Hollis Blanchard wrote:
> > 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.
> >   
> 
> Is Xen ppc discontinued?

I have no plans to continue development; I can't speak for anybody else.

> > 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.
> 
> It doesn't have to be a package; it can be as simple as a tarball that 
> people have to make; && sudo make install before compiling kvm, the same 
> as other prerequisite libraries.

Sure. Let's put that tarball inside the qemu directory, and then have it
extracted and built automatically when the user types "make".

I'm really not clear on what advantage you think will be gained here.

> The barrier should be whether we need to carry local changes or not.  If 
> we can use upstream as is, then it should be installed independently.

So let me get this straight... you think it's cool to awk kernel source,
but not to copy library code that was designed to be copied in the first
place? Seriously? Would it be more palatable to you if I ran awk over
arch/powerpc/boot/libdft?

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

  reply	other threads:[~2008-02-27 19:57 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
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               ` Hollis Blanchard [this message]
2008-02-28  8:16                 ` [kvm-ppc-devel] " 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=1204142247.2532.70.camel@basalt \
    --to=hollisb@us.ibm.com \
    --cc=avi@qumranet.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