Menu
▾
▴
xen-devel
|
From: Hollis B. <ho...@us...> - 2005-03-23 22:01:54
Attachments:
xen-headers.diff
|
I think this is the last of the header fixes I've run across. Though it's sometimes difficult to tell, I believe Xen/ia64 has asm/mm.h, flushtlb.h, page.h, and shadow.h. Please apply. Signed-off-by: Hollis Blanchard <ho...@us...> -- Hollis Blanchard IBM Linux Technology Center |
|
From: Keir F. <Kei...@cl...> - 2005-03-24 08:51:27
|
One of the two additions was already applied. I think the other, to softirq.h, was a problem for ia64? -- Keir On 23 Mar 2005, at 22:01, Hollis Blanchard wrote: > I think this is the last of the header fixes I've run across. Though > it's > sometimes difficult to tell, I believe Xen/ia64 has asm/mm.h, > flushtlb.h, > page.h, and shadow.h. Please apply. > > Signed-off-by: Hollis Blanchard <ho...@us...> > > -- > Hollis Blanchard > IBM Linux Technology Center > <xen-headers.diff> |
|
From: Hollis B. <ho...@us...> - 2005-03-24 14:47:16
Attachments:
xen-more-headers.diff
|
On Mar 24, 2005, at 2:54 AM, Keir Fraser wrote: > One of the two additions was already applied. I think the other, to > softirq.h, was a problem for ia64? Sorry, I sent the wrong patch. The correct one is attached now. Signed-off-by: Hollis Blanchard <ho...@us...> -- Hollis Blanchard IBM Linux Technology Center |
|
From: Dan M. <dan...@hp...> - 2005-03-24 20:40:57
|
Sorry for the delay in comment... I was traveling and am a bit behind on email. This second patch looks good to me, though I would prefer to change to '#include <asm/regs.h>' from 'struct xen_regs;' as xen_regs is #define'd to pt_regs on ia64 and the explicit use of struct xen_regs in a header could cause header ordering problems later. Will that work for ppc? Dan |
|
From: Hollis B. <ho...@us...> - 2005-03-24 21:04:18
|
On Thursday 24 March 2005 14:40, Dan Magenheimer wrote: > This second patch looks good to me, though I would prefer > to change to '#include <asm/regs.h>' from 'struct xen_regs;' > as xen_regs is #define'd to pt_regs on ia64 and the explicit > use of struct xen_regs in a header could cause header ordering > problems later. Will that work for ppc? Ah, sure... I was just trying to avoid extra dependency trees where possible. Apparently it is not possible here. :) So that should be #include <public/xen.h> (which includes arch-*.h which defines xen_regs). It looks like we may want to move ia64's #define to arch-ia64.h ... -- Hollis Blanchard IBM Linux Technology Center |
|
From: Christian L. <chr...@gm...> - 2005-03-24 21:24:33
|
On Thu, 24 Mar 2005 15:03:19 -0600, Hollis Blanchard <ho...@us...> wrote:
> On Thursday 24 March 2005 14:40, Dan Magenheimer wrote:
> > This second patch looks good to me, though I would prefer
> > to change to '#include <asm/regs.h>' from 'struct xen_regs;'
> > as xen_regs is #define'd to pt_regs on ia64 and the explicit
> > use of struct xen_regs in a header could cause header ordering
> > problems later. Will that work for ppc?
>
> Ah, sure... I was just trying to avoid extra dependency trees where possible.
> Apparently it is not possible here. :)
>
> So that should be #include <public/xen.h> (which includes arch-*.h which
> defines xen_regs). It looks like we may want to move ia64's #define to
> arch-ia64.h ...
Could you please include asm/regs.h or public/xen.h wherever you want
to include keyhandler.h? Thanks.
christian
|
|
From: Hollis B. <ho...@us...> - 2005-03-25 16:25:16
|
On Thu, 2005-03-24 at 21:24 +0000, Christian Limpach wrote: > On Thu, 24 Mar 2005 15:03:19 -0600, Hollis Blanchard <ho...@us...> wrote: > > On Thursday 24 March 2005 14:40, Dan Magenheimer wrote: > > > This second patch looks good to me, though I would prefer > > > to change to '#include <asm/regs.h>' from 'struct xen_regs;' > > > as xen_regs is #define'd to pt_regs on ia64 and the explicit > > > use of struct xen_regs in a header could cause header ordering > > > problems later. Will that work for ppc? > > > > Ah, sure... I was just trying to avoid extra dependency trees where possible. > > Apparently it is not possible here. :) > > > > So that should be #include <public/xen.h> (which includes arch-*.h which > > defines xen_regs). It looks like we may want to move ia64's #define to > > arch-ia64.h ... > > Could you please include asm/regs.h or public/xen.h wherever you want > to include keyhandler.h? Thanks. That works great, until somebody other than me includes or modifies keyhandler.h (or any of the other headers we've been talking about). I guess I don't see the difficulty in making sure you include what you use...? -- Hollis Blanchard IBM Linux Technology Center |
|
From: Christian L. <chr...@gm...> - 2005-03-26 02:15:03
|
On Fri, 25 Mar 2005 10:22:50 -0600, Hollis Blanchard <ho...@us...> wrote:
> On Thu, 2005-03-24 at 21:24 +0000, Christian Limpach wrote:
> > On Thu, 24 Mar 2005 15:03:19 -0600, Hollis Blanchard <ho...@us...> wrote:
> > > On Thursday 24 March 2005 14:40, Dan Magenheimer wrote:
> > > > This second patch looks good to me, though I would prefer
> > > > to change to '#include <asm/regs.h>' from 'struct xen_regs;'
> > > > as xen_regs is #define'd to pt_regs on ia64 and the explicit
> > > > use of struct xen_regs in a header could cause header ordering
> > > > problems later. Will that work for ppc?
> > >
> > > Ah, sure... I was just trying to avoid extra dependency trees where possible.
> > > Apparently it is not possible here. :)
> > >
> > > So that should be #include <public/xen.h> (which includes arch-*.h which
> > > defines xen_regs). It looks like we may want to move ia64's #define to
> > > arch-ia64.h ...
> >
> > Could you please include asm/regs.h or public/xen.h wherever you want
> > to include keyhandler.h? Thanks.
>
> That works great, until somebody other than me includes or modifies
> keyhandler.h (or any of the other headers we've been talking about).
>
> I guess I don't see the difficulty in making sure you include what you
> use...?
I think we have too many header files which include other header files
already -- to the point that a lot of .c files don't include all the
header files they need because some random header file includes it for
them.
keyhandler.c is one of the header files you probably want to include
in source code level add-on software, software which might be require
using a header set which is not compatible with Xen's header set.
christian
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X