mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Deegan <tim@xen.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jan Beulich <JBeulich@suse.com>, "Keir (Xen.org)" <keir@xen.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH LINUX] xen: event channel arrays are xen_ulong_t and not unsigned long
Date: Tue, 19 Feb 2013 17:26:45 +0000	[thread overview]
Message-ID: <20130219172645.GA97631@ocelot.phlegethon.org> (raw)
In-Reply-To: <1361294248.1051.136.camel@zakaz.uk.xensource.com>

At 17:17 +0000 on 19 Feb (1361294248), Ian Campbell wrote:
> On Tue, 2013-02-19 at 17:11 +0000, Stefano Stabellini wrote:
> > On Tue, 19 Feb 2013, Ian Campbell wrote:
> > > +/*
> > > + * We cannot use xchg because it does not support 8-byte
> > > + * values. However it is safe to use {ldr,dtd}exd directly because all
> > > + * platforms which Xen can run on support those instructions.
> > > + */
> > > +static inline xen_ulong_t xchg_xen_ulong(xen_ulong_t *ptr, xen_ulong_t val)
> > > +{
> > > +       xen_ulong_t oldval;
> > > +       unsigned int tmp;
> > > +
> > > +       wmb();
> > > +       asm volatile("@ read_evtchn_pending_sel\n"
> >                            ^ do we need this?
> 
> It means that the .s files (if you create them) and such are a bit more
> readable, it's not that uncommon in the ARM inline assembly.

+1.  s/read_evtchn_pending_sel/xchg_xen_ulong/ though.

Tim.

  reply	other threads:[~2013-02-19 17:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19 14:48 [PATCH V2] " Ian Campbell
2013-02-19 14:49 ` [PATCH LINUX] " Ian Campbell
2013-02-19 17:11   ` Stefano Stabellini
2013-02-19 17:17     ` Ian Campbell
2013-02-19 17:26       ` Tim Deegan [this message]
2013-02-19 17:28         ` Ian Campbell
2013-02-19 14:49 ` [PATCH XEN] " Ian Campbell
2013-02-19 16:42   ` Stefano Stabellini
2013-02-21 17:16   ` Ian Campbell
2013-02-21 18:43     ` Keir Fraser
2013-02-22  8:28       ` Ian Campbell
2013-02-22  8:12     ` Jan Beulich
2013-02-22  8:28       ` Ian Campbell
2013-02-22  8:48         ` Jan Beulich
2013-02-22  8:55           ` Ian Campbell
2013-02-22  9:05             ` Jan Beulich
2013-02-19 17:27 ` [PATCH LINUX v3] " Ian Campbell
2013-02-19 17:29 ` [PATCH LINUX v4] " Ian Campbell
2013-02-19 18:12   ` Stefano Stabellini
2013-02-19 18:43     ` Konrad Rzeszutek Wilk
2013-02-20  2:07   ` Konrad Rzeszutek Wilk
2013-02-20  3:09     ` Konrad Rzeszutek Wilk
2013-02-20  9:13       ` Ian Campbell
2013-02-20 11:48 ` [PATCH LINUX v5] " Ian Campbell
2013-02-21 17:11   ` Stefano Stabellini
2013-03-04  2:45   ` Rob Herring
2013-03-05  3:04     ` Will Deacon
2013-03-05  3:45       ` Ian Campbell
2013-03-05  6:55       ` Rob Herring
2013-03-05  7:03         ` Ian Campbell
2013-03-05  8:08         ` Will Deacon
2013-03-05  9:29           ` Ian Campbell
2013-03-07  3:17             ` Will Deacon
2013-03-07  7:17               ` Ian Campbell
2013-03-05  3:56     ` Ian Campbell
2013-03-05 14:04       ` Konrad Rzeszutek Wilk

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=20130219172645.GA97631@ocelot.phlegethon.org \
    --to=tim@xen.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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

all inboxes | Powered by JetHome®