All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Iurii Konovalenko <iurii.konovalenko@globallogic.com>
Cc: Julien Grall <julien.grall@citrix.com>,
	stefano.stabellini@eu.citrix.com, tim@xen.org,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v3] arm: irq: increase size of irq from uint8_t to uint32_t
Date: Wed, 15 Apr 2015 13:10:08 +0100	[thread overview]
Message-ID: <1429099808.15516.240.camel@citrix.com> (raw)
In-Reply-To: <1428502459-19821-2-git-send-email-oiurii.konovalenko@globallogic.com>

Switching Julien to his Citrix address which should probably be used in
the future.

On Wed, 2015-04-08 at 17:14 +0300, Iurii Konovalenko wrote:
> From: Iurii Konovalenko <iurii.konovalenko@globallogic.com>
> 
> Changes are dedicated to XEN_DOMCTL_irq_permission and
> IRQ pssthrough API functions.
> 
> PHYSDEV_* operations already using 32 bits type but signed one.
> 
> Although, PHYSDEV_* operations are not yet used on ARM and LPIs support
> (which are using very high number) are not supported yet, we don't need
> to care about theses for now.

I may have slightly lost track, but I think we decided in Julien's
passthrough thread not to use most of these interfaces on ARM, or am I
confused?

If I'm correct then I think we can avoid messing with many of other
ones, for example the ISA IRQ one doesn't need changing, does it? (ISA
only had 16 IRQs IIRC...)

I think it would be best if whichever bits of this are still relevant
were folded into Julien's '[PATCH v5 p2 04/19] xen/arm: Implement
hypercall DOMCTL_{,un}bind_pt_pirq' or at least presented as a followup
to it.

> diff --git a/xen/include/public/domctl.h b/xen/include/public/domctl.h
> index 8803ab2..65fb866 100644
> --- a/xen/include/public/domctl.h
> +++ b/xen/include/public/domctl.h
> @@ -400,7 +400,7 @@ DEFINE_XEN_GUEST_HANDLE(xen_domctl_setdebugging_t);
>  
>  /* XEN_DOMCTL_irq_permission */
>  struct xen_domctl_irq_permission {
> -    uint8_t pirq;
> +    uint32_t pirq;
>      uint8_t allow_access;    /* flag to specify enable/disable of IRQ access */

I think we weren't going to end up using this one either, but again I
might not be remembering correctly.

Ian.

  reply	other threads:[~2015-04-15 12:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 14:14 [PATCH v3] increase size of irq from uint8_t to uint32_t Iurii Konovalenko
2015-04-08 14:14 ` [PATCH v3] arm: irq: " Iurii Konovalenko
2015-04-15 12:10   ` Ian Campbell [this message]
2015-04-15 13:00     ` Julien Grall
2015-04-15 13:18       ` Ian Campbell
2015-06-26 10:10 ` [PATCH v3] " Julien Grall

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=1429099808.15516.240.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=iurii.konovalenko@globallogic.com \
    --cc=julien.grall@citrix.com \
    --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.