All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	IanJackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	David Vrabel <david.vrabel@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] have architectures specify the number of PIRQs a hardware domain gets
Date: Fri, 5 Dec 2014 14:51:01 +0000	[thread overview]
Message-ID: <1417791061.22808.68.camel@eu.citrix.com> (raw)
In-Reply-To: <5481D3D1020000780004D35F@mail.emea.novell.com>

On Fri, 2014-12-05 at 14:48 +0000, Jan Beulich wrote:
> >>> On 05.12.14 at 15:27, <Ian.Campbell@eu.citrix.com> wrote:
> > On Fri, 2014-12-05 at 13:51 +0000, Jan Beulich wrote:
> >>  #define nr_static_irqs NR_IRQS
> >> +#define arch_hwdom_irqs(domid) NR_IRQS
> > 
> > FWIW gic_number_lines() is the ARM equivalent of getting the number of
> > GSIs.
> > 
> > *BUT* we don't actually use pirqs on ARM (everything goes via the
> > virtualised interrupt controller). So maybe we should be setting
> > nr_pirqs to 0 on ARM. I appreciate you likely want such a patch to come
> > from an ARM person, so I'm fine with you making this NR_IRQS in the
> > meantime.
> 
> Considering Julien also asking for this, I don't mind changing this to
> zero for ARM. Just let me know which way I can get this ack-ed.

If you are happy to provide a version using zero and Julien wants to
provide a tested-by then I'm fine with going that way.

I'm not happy taking that change untested though, and I don't expect you
to test it.

Ian.

  reply	other threads:[~2014-12-05 14:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 13:51 [PATCH] have architectures specify the number of PIRQs a hardware domain gets Jan Beulich
2014-12-05 14:27 ` Ian Campbell
2014-12-05 14:36   ` Julien Grall
2014-12-05 14:42     ` Ian Campbell
2014-12-05 15:25       ` Julien Grall
2014-12-05 15:42         ` Jan Beulich
2014-12-05 16:05           ` Julien Grall
2014-12-05 16:23             ` Jan Beulich
2014-12-05 16:34               ` Stefano Stabellini
2014-12-05 14:48   ` Jan Beulich
2014-12-05 14:51     ` Ian Campbell [this message]
2014-12-11 12:07       ` Ian Campbell
2014-12-11 13:16         ` Jan Beulich
2014-12-05 14:48 ` David Vrabel
2014-12-05 14:54   ` Jan Beulich

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=1417791061.22808.68.camel@eu.citrix.com \
    --to=ian.campbell@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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.