From: David Vrabel <david.vrabel@citrix.com> To: Boris Ostrovsky <boris.ostrovsky@oracle.com>, <konrad.wilk@oracle.com>, <david.vrabel@citrix.com>, <linux@arm.linux.org.uk> Cc: <jgross@suse.com>, <linux-kernel@vger.kernel.org>, <xen-devel@lists.xen.org>, <stefano.stabellini@citrix.com>, <tglx@linutronix.de>, <vkuznets@redhat.com>, <linux-arm-kernel@lists.infradead.org> Subject: Re: [Xen-devel] [PATCH] xen/events: Always allocate legacy interrupts on PV guests Date: Thu, 26 Nov 2015 18:22:27 +0000 [thread overview] Message-ID: <56574DE3.2040808@citrix.com> (raw) In-Reply-To: <1448036704-18630-1-git-send-email-boris.ostrovsky@oracle.com> On 20/11/15 16:25, Boris Ostrovsky wrote: > After commit 8c058b0b9c34 ("x86/irq: Probe for PIC presence before > allocating descs for legacy IRQs") early_irq_init() will no longer > preallocate descriptors for legacy interrupts if PIC does not > exist, which is the case for Xen PV guests. > > Therefore we may need to allocate those descriptors ourselves. Applied to for-linus-4.4, thanks. > --- a/arch/arm64/include/asm/irq.h > +++ b/arch/arm64/include/asm/irq.h > @@ -7,4 +7,10 @@ struct pt_regs; > > extern void set_handle_irq(void (*handle_irq)(struct pt_regs *)); > > +#define NR_IRQS_LEGACY 0 I dropped this unnecessary #define. David
WARNING: multiple messages have this Message-ID (diff)
From: david.vrabel@citrix.com (David Vrabel) To: linux-arm-kernel@lists.infradead.org Subject: [Xen-devel] [PATCH] xen/events: Always allocate legacy interrupts on PV guests Date: Thu, 26 Nov 2015 18:22:27 +0000 [thread overview] Message-ID: <56574DE3.2040808@citrix.com> (raw) In-Reply-To: <1448036704-18630-1-git-send-email-boris.ostrovsky@oracle.com> On 20/11/15 16:25, Boris Ostrovsky wrote: > After commit 8c058b0b9c34 ("x86/irq: Probe for PIC presence before > allocating descs for legacy IRQs") early_irq_init() will no longer > preallocate descriptors for legacy interrupts if PIC does not > exist, which is the case for Xen PV guests. > > Therefore we may need to allocate those descriptors ourselves. Applied to for-linus-4.4, thanks. > --- a/arch/arm64/include/asm/irq.h > +++ b/arch/arm64/include/asm/irq.h > @@ -7,4 +7,10 @@ struct pt_regs; > > extern void set_handle_irq(void (*handle_irq)(struct pt_regs *)); > > +#define NR_IRQS_LEGACY 0 I dropped this unnecessary #define. David
next prev parent reply other threads:[~2015-11-26 18:22 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-11-20 16:25 [PATCH] xen/events: Always allocate legacy interrupts on PV guests Boris Ostrovsky 2015-11-20 16:25 ` Boris Ostrovsky 2015-11-20 16:35 ` Stefano Stabellini 2015-11-20 16:35 ` Stefano Stabellini 2015-11-24 14:36 ` Boris Ostrovsky 2015-11-24 14:36 ` Boris Ostrovsky 2015-11-24 14:36 ` Boris Ostrovsky 2015-11-20 16:35 ` Stefano Stabellini 2015-11-26 18:22 ` David Vrabel 2015-11-26 18:22 ` David Vrabel [this message] 2015-11-26 18:22 ` [Xen-devel] " David Vrabel -- strict thread matches above, loose matches on Subject: below -- 2015-11-17 15:36 Boris Ostrovsky 2015-11-18 11:16 ` [Xen-devel] " Vitaly Kuznetsov 2015-11-18 14:03 ` Boris Ostrovsky 2015-11-18 14:28 ` Vitaly Kuznetsov 2015-11-18 15:00 ` Boris Ostrovsky
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=56574DE3.2040808@citrix.com \ --to=david.vrabel@citrix.com \ --cc=boris.ostrovsky@oracle.com \ --cc=jgross@suse.com \ --cc=konrad.wilk@oracle.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=stefano.stabellini@citrix.com \ --cc=tglx@linutronix.de \ --cc=vkuznets@redhat.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: linkBe 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.