All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: Christian Limpach <Christian.Limpach@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: [PATCH] Re: [Xen-staging] [xen-unstable] [qemu] Removeatomic_set_bit, atomic_clear_bit and ia64_intrinsic.h and its
Date: Thu, 10 May 2007 15:09:47 -0600	[thread overview]
Message-ID: <1178831387.27751.31.camel@bling> (raw)
In-Reply-To: <0326530267625D42A4E36594FDD0D1437576D2@exchpamain.ad.xensource.com>

On Thu, 2007-05-10 at 13:01 -0700, Christian Limpach wrote:
> >    ia64intrin.h is all but empty in gcc 4.1.2, so there's no point in
> > including it.  dm-exec is still making use of a few of these 
> > too, but I
> > guess it's easy enough to inline them there.  Patch below.  Thanks,
> 
> Would it also work to just leave the include in exec-all.h?  I was
> confused and thought that it was a local include which is why I put
> #ifndef CONFIG_DM around all the testandset definitions.
> 
> So, if I remove the #ifndef CONFIG_DM, anything including exec-all.h
> should still compile, right?  Do I still need the extra #define's in
> that case?

   ia64intrin.h is basically empty, so making it included for the
dm-exec build doesn't really help.  The defines still need to come from
somewhere.  We could replace <ia64intrin.h> with <asm/gcc_intrin.h>, but
for this trivial case, I'd rather not get tied up including kernel
headers in userspace tools.  Thanks,

	Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.

      reply	other threads:[~2007-05-10 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200705101500.l4AF0N4b027027@latara.uk.xensource.com>
2007-05-10 16:35 ` [PATCH] Re: [Xen-staging] [xen-unstable] [qemu] Remove atomic_set_bit, atomic_clear_bit and ia64_intrinsic.h and its Alex Williamson
2007-05-10 20:01   ` [PATCH] Re: [Xen-staging] [xen-unstable] [qemu] Removeatomic_set_bit, " Christian Limpach
2007-05-10 21:09     ` Alex Williamson [this message]

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=1178831387.27751.31.camel@bling \
    --to=alex.williamson@hp.com \
    --cc=Christian.Limpach@xensource.com \
    --cc=xen-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 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.