All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>,
	xen-devel@lists.xensource.com
Cc: xen-ia64-devel@lists.xensource.com
Subject: Re: [PATCH][QEMU] Add IA64-specific code for new qemu.
Date: Wed, 26 Jul 2006 20:24:00 +0900	[thread overview]
Message-ID: <2FC6B0A5FE3BFEtakebe_akio@jp.fujitsu.com> (raw)
In-Reply-To: <CA502B3E9EE27B4490C87C12E3C7C8510B25BF@pdsmsx412.ccr.corp.intel.com>

Hi, Xiantao

Is the following testandset redefine?

diff -r bbabdebc54ad tools/ioemu/exec-all.h
--- a/tools/ioemu/exec-all.h	Wed Jul 19 21:13:36 2006 +0100
+++ b/tools/ioemu/exec-all.h	Tue Jul 25 09:30:05 2006 +0800
@@ -391,6 +391,15 @@ static inline int testandset (int *p)
 }
 #endif
 
+#ifdef __ia64__
+#include "ia64_intrinsic.h"
+static inline int testandset (int *p)
+{
+    uint32_t o = 0, n = 1;
+    return (int)cmpxchg_acq(p, o, n);
+}
+#endif
+
 #ifdef __s390__
 static inline int testandset (int *p)
 {
 
Best Regards,

Akio Takebe

>This patch adds the ia64-specific code for new Qemu .
>In addition, some ia64 patches aren't checked into xen-unstable.hg, so I
>reversed the related logic temporarily. Once sync with
>xen-ia64-unstable.hg, the logic will regain automatically.
>Thanks & Best Regards
>-Xiantao
>
>OTC,Intel Corporation
>
>
>-------------------------------text/plain-------------------------------
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@lists.xensource.com
>http://lists.xensource.com/xen-ia64-devel

  reply	other threads:[~2006-07-26 11:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25  2:09 [PATCH][QEMU] Add IA64-specific code for new qemu Zhang, Xiantao
2006-07-26 11:24 ` Akio Takebe [this message]
2006-07-26 12:41   ` Re: [Xen-ia64-devel] " Christian Limpach
2006-07-26 17:20     ` Alex Williamson
2006-07-26 18:34       ` Alex Williamson
2006-07-26 20:14       ` Christian Limpach
2006-07-26 12:41 ` Christian Limpach

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=2FC6B0A5FE3BFEtakebe_akio@jp.fujitsu.com \
    --to=takebe_akio@jp.fujitsu.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-devel@lists.xensource.com \
    --cc=xiantao.zhang@intel.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.