From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [kvm-ppc-devel] Current e500 kvm guest kernel booting log
Date: Tue, 18 Dec 2007 02:33:58 +0000 [thread overview]
Message-ID: <1197945239.5026.12.camel@diesel> (raw)
In-Reply-To: <ABF87B0B6A38C0458E319AC973ED68AEA21127@zch01exm26.fsl.freescale.net>
On Fri, 2007-12-14 at 14:15 +0800, Zhang Wei wrote:
> > Hollis Blanchard wrote:
> > > On Thu, 2007-12-13 at 18:14 +0800, Zhang Wei wrote:
> > >>> From: Hollis Blanchard [mailto:hollisb@us.ibm.com]
> > >>>>> We haven't touched the "hack" code recently, since we've been
> > >>>>> refactoring the upstream tree. That's pretty much done
> > >>>>> though, and right
> > >>>>> now I'm just starting to integrate the old 440 support with the
> > >>>>> new upstream code. That's not in a good state right now, but I
> > >>>>> could clean it up and send it out if you're interested.
> > >>>>
> > >>>> Yes! I think hack codes are only for verifying the idea. Our
> > >>>> target is for upstream code. I hope I could join you!
> > >>>
> > >>> Well, unfortunately at the moment I'm just fighting with
> > >>> asm-offsets.h . :( Since I'm basically already on vacation,
> > >>> I'm not sure
> > >>> I'll be able to get anything ready until January.
> > >>>
> > >>
> > >> Do you mind send out the asm-offsets.h? Maybe I can take it base on
> > >> the hack code.
> > >
> > > Oh, the file is the same. The problem is how to have Kbuild
> > > automatically generate it.
> >
> > IA64 have the same issues , do you have good idea to handle
> > it ? Now, I
> > let kvm makefile to call a extenal script to solve it. :)
> >
>
> Do you mean if you change the struct kvm_vcpu of the kvm.h file, but the
> asm-offsets.h file can not be re-generated by your current Makefile?
>
> If it is, you can modify Makefile as below:
> - $(obj)/kvm-offsets.s: $(src)/kvm-offsets.c
> + $(obj)/kvm-offsets.s: $(src)/kvm-offsets.c FORCE
>
> Or is there any other problems about asm-offsets.h in Makefile?
Yes, there is a larger problem: forget the dependencies; how do we
generate asm-offsets.h in the first place? The Makefile hackery that
I've posted before is not a good solution, and I'm looking for that good
solution.
IA64 needs to generate its own asm-offsets too, and so does lguest.
That's why I've been looking at the "mkasm-values" patches recently
(google it)...
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
next prev parent reply other threads:[~2007-12-18 2:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 5:01 [kvm-ppc-devel] Current e500 kvm guest kernel booting log Zhang Wei
2007-12-11 15:41 ` Hollis Blanchard
2007-12-12 11:57 ` Zhang Wei
2007-12-12 19:19 ` Hollis Blanchard
2007-12-13 10:14 ` Zhang Wei
2007-12-14 0:01 ` Hollis Blanchard
2007-12-14 3:47 ` Zhang, Xiantao
2007-12-14 6:15 ` Zhang Wei
2007-12-18 2:33 ` Hollis Blanchard [this message]
2007-12-18 2:52 ` Zhang, Xiantao
2007-12-18 2:52 ` Zhang, Xiantao
[not found] ` <42DFA526FC41B1429CE7279EF83C6BDCB131B6-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-18 10:04 ` [kvm-ppc-devel] [kvm-devel] Current e500 kvm guest kernel Christian Ehrhardt
2007-12-18 10:04 ` [kvm-ppc-devel] Current e500 kvm guest kernel booting log Christian Ehrhardt
[not found] ` <47679B11.8070604-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-12-19 8:50 ` [kvm-ppc-devel] [kvm-devel] Current e500 kvm guest kernel Zhang Wei
2007-12-19 8:50 ` [kvm-ppc-devel] Current e500 kvm guest kernel booting log Zhang Wei
2007-12-18 3:40 ` Zhang Wei
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=1197945239.5026.12.camel@diesel \
--to=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.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.