All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: julien.grall@linaro.org, tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH RFC] xen: arm: context switch vtimer PPI state.
Date: Tue, 3 Mar 2015 12:26:20 +0000	[thread overview]
Message-ID: <1425385580.24959.144.camel@citrix.com> (raw)
In-Reply-To: <1425385132.24959.139.camel@citrix.com>

On Tue, 2015-03-03 at 12:18 +0000, Ian Campbell wrote:
> > > > > > +    /* Xen s/w state */
> > > > > > +    unsigned long inprogress:1;
> > > > > > +};
> > > > 
> > > > Using a uint32_t bitmask would be more in line the rest of the code
> > > > style, but it is just a matter of taste.
> > > 
> > > You mean "uint32_t inprogress:1" for each? Or
> > > #define ENAVBLED 1
> > > #define PENDING 2
> > > etc
> > > and test_set_bit stuff?
> >  
> > Something like status in xen/include/asm-arm/vgic.h:struct pending_irq
> 
> OK.

Actually, what is the benefit? I think pending_irq.status is done this
way because it is used lock free from multiple contexts and this allows
for test_and_set_bit etc to be used.

The hwppi state isn't accessed like that, so I think using the normal
appropriate types like we do in stuct arch_{domain,vcpu} is the
appropriate style. struct hwppi_state is even defined in domain.h.

Ian.

  reply	other threads:[~2015-03-03 12:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 15:55 [PATCH RFC] xen: arm: context switch vtimer PPI state Ian Campbell
2015-01-27 13:16 ` Julien Grall
2015-01-27 13:34   ` Ian Campbell
2015-01-27 13:47     ` Julien Grall
2015-02-10  2:59 ` Ian Campbell
2015-03-02 18:42   ` Stefano Stabellini
2015-03-03 11:56     ` Ian Campbell
2015-03-03 12:00       ` Stefano Stabellini
2015-03-03 12:18         ` Ian Campbell
2015-03-03 12:26           ` Ian Campbell [this message]
2015-03-09 17:48           ` Stefano Stabellini
2015-03-03 11:38 ` Stefano Stabellini
2015-03-03 11:51   ` Ian Campbell
2015-03-03 11:55     ` Stefano Stabellini

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=1425385580.24959.144.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --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 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.