All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	xen-ppc-devel <xen-ppc-devel@lists.xensource.com>
Subject: Re: Re: [Xen-changelog] [xen-unstable] xen: Split domain_flags into discrete first-class fields in the
Date: Thu, 05 Apr 2007 17:59:22 +0100	[thread overview]
Message-ID: <C23AE97A.CE10%keir@xensource.com> (raw)
In-Reply-To: <C23ADAC6.CDFE%keir@xensource.com>

On 5/4/07 16:56, "Keir Fraser" <keir@xensource.com> wrote:

> On 5/4/07 16:44, "Hollis Blanchard" <hollisb@us.ibm.com> wrote:
> 
>> This is an interface problem: using the interface in a way that works on
>> x86 fails on other architectures. PLEASE let's redefine the interface to
>> prevent this from happening. In this case, that means replacing the
>> xchg() macro with
>>         static inline xchg(atomic_t *ptr, atomic_t val)
>> and changing the type of 'is_dying'.
> 
> Just need to define bool_t appropriately. What do you need: a long?

Does PowerPC support atomic byte loads and stores by the way (i.e.,
concurrent loads and stores to adjacent bytes by different processors do not
conflict with each other)? In which case it might be worth keeping bool_t
and defining atomic_bool_t or atomic_rmw_bool_t for bools that need to be
atomically read-modified-written. That would avoid bloating critical
structures for the few bools that need atomic r-m-w semantics.

 -- Keir

  reply	other threads:[~2007-04-05 16:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200703302310.l2UNAF7O021926@xenbits2.xensource.com>
2007-04-05 15:44 ` [Xen-changelog] [xen-unstable] xen: Split domain_flags into discrete first-class fields in the Hollis Blanchard
2007-04-05 15:56   ` Keir Fraser
2007-04-05 16:59     ` Keir Fraser [this message]
2007-04-05 17:21       ` Hollis Blanchard
2007-04-05 17:08     ` Hollis Blanchard

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=C23AE97A.CE10%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=hollisb@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ppc-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.