xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@XenSource.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Alex Williamson <alex.williamson@hp.com>,
	xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] ia64 build fixes
Date: Sun, 02 Apr 2006 09:37:19 +0100	[thread overview]
Message-ID: <1143967039.4547.5.camel@localhost.localdomain> (raw)
In-Reply-To: <cbc762bbf18d3861589570c651a7213e@cl.cam.ac.uk>

On Sun, 2006-04-02 at 09:20 +0100, Keir Fraser wrote:
> On 1 Apr 2006, at 22:46, Alex Williamson wrote:
> 
> >    Here's a patch that enables HYPERVISOR_sched_op() and
> > HYPERVISOR_sched_opt_compat() for ia64.  We currently have no users of
> > this call, but there's no harm in enabling it (tested by adding a
> > HYPERVISOR_yield() call to default_idle()).  I did notice a problem 
> > with
> > the compat interface though, nothing defines __XEN_INTERFACE_VERSION__
> > for the build of xen.  We're therefore stuck on interface version
> > 0x00000000 where __HYPERVISOR_sched_op_compat == __HYPERVISOR_sched_op.
> 
> Well, it doesn't actually matter right now since Xen itself does not 
> use the __HYPERVISOR_foo numbers. But yes, I can see this might bite us 
> later so we ought to define it.

I was using them in some debugging code the other day and it bit me :-( 

Christian suggested changing xen-compat.h to use the maximum version
when compiling Xen. e.g.
        
        #ifndef __XEN_INTERFACE_VERSION__
        #ifdef __XEN__
        #define __XEN_INTERFACE_VERSION__ 0xffffffff
        #else
        #define __XEN_INTERFACE_VERSION__ 0x00000000
        #endif
        #endif

Ian.

  parent reply	other threads:[~2006-04-02  8:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 23:44 [PATCH] ia64 build fixes Alex Williamson
2006-04-01 10:10 ` Keir Fraser
2006-04-01 21:46   ` Alex Williamson
2006-04-02  8:20     ` Keir Fraser
2006-04-02  8:31       ` Keir Fraser
2006-04-02  8:37       ` Ian Campbell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-03  2:45 Tian, Kevin
2006-04-25 19:59 Benson, Ronald A

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=1143967039.4547.5.camel@localhost.localdomain \
    --to=ian.campbell@xensource.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=alex.williamson@hp.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-devel@lists.xensource.com \
    /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;
as well as URLs for NNTP newsgroup(s).