From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: david.vrabel@citrix.com, konrad.wilk@oracle.com, jgross@suse.com,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
xen-devel@lists.xen.org
Subject: Re: [Xen-devel] [PATCH] xen/events: Always allocate legacy interrupts on PV guests
Date: Wed, 18 Nov 2015 10:00:35 -0500 [thread overview]
Message-ID: <564C9293.8070703@oracle.com> (raw)
In-Reply-To: <87d1v7v0t8.fsf@vitty.brq.redhat.com>
On 11/18/2015 09:28 AM, Vitaly Kuznetsov wrote:
> Boris Ostrovsky <boris.ostrovsky@oracle.com> writes:
>
>> On 11/18/2015 06:16 AM, Vitaly Kuznetsov wrote:
>>> Boris Ostrovsky <boris.ostrovsky@oracle.com> writes:
>>>
>>>> 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 PIT does not
>>>> exist.
>>> PIC?
>> Right. David, can you fix this before committing?
>>
>>>> Therefore we need to allocate those descriptors for PV guests
>>>> ourselves.
>>>>
>>>> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>>>> Suggested-by: Thomas Gleixner <tglx@linutronix.de>
>>>> ---
>>>> drivers/xen/events/events_base.c | 8 ++++----
>>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>>>
>>>> diff --git a/drivers/xen/events/events_base.c b/drivers/xen/events/events_base.c
>>>> index 849500e..a2bb333 100644
>>>> --- a/drivers/xen/events/events_base.c
>>>> +++ b/drivers/xen/events/events_base.c
>>>> @@ -419,8 +419,8 @@ static int __must_check xen_allocate_irq_gsi(unsigned gsi)
>>>> if (xen_pv_domain() && !xen_initial_domain())
>>>> return xen_allocate_irq_dynamic();
>>>>
>>>> - /* Legacy IRQ descriptors are already allocated by the arch. */
>>>> - if (gsi < NR_IRQS_LEGACY)
>>>> + /* On HVM legacy IRQ descriptors are already allocated by the arch. */
>>>> + if (xen_hvm_domain() && gsi < NR_IRQS_LEGACY)
>>>> irq = gsi;
>>> Wouldn't it be better to write it as
>>> if (gsi < nr_legacy_irqs()) ?
>> I don't think so: on PV we end up setting legacy_pic to
>> null_legacy_pic in probe_8259A() and that will make nr_legacy_irqs()
>> return 0.
> Yes, so the condition will always be false for PV and it equals to
> xen_hvm_domain() or am I missng something?
Oh, I see what you are saying. Yes, it would be cleaner.
-boris
>
>>> I think it's possible to have PIC-less HVM guests in future (btw, what
>>> about HVMlite?). I see nr_legacy_irqs() is x86-only but it can easily be
>>> defined to NR_IRQS_LEGACY on other arches.
>>>
next prev parent reply other threads:[~2015-11-18 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 15:36 [PATCH] xen/events: Always allocate legacy interrupts on PV guests Boris Ostrovsky
2015-11-17 15:38 ` David Vrabel
2015-11-17 16:24 ` Juergen Gross
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-20 16:25 Boris Ostrovsky
2015-11-26 18:22 ` [Xen-devel] " David Vrabel
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=564C9293.8070703@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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: 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