All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: jgross@suse.com, linux-kernel@vger.kernel.org,
	xen-devel@lists.xen.org, david.vrabel@citrix.com,
	tglx@linutronix.de
Subject: Re: [PATCH] xen/events: Always allocate legacy interrupts on PV guests
Date: Wed, 18 Nov 2015 15:28:51 +0100	[thread overview]
Message-ID: <87d1v7v0t8.fsf__25444.1839679659$1447857032$gmane$org@vitty.brq.redhat.com> (raw)
In-Reply-To: <564C8531.2000608@oracle.com> (Boris Ostrovsky's message of "Wed, 18 Nov 2015 09:03:29 -0500")

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?

>
>>
>> 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.
>
> Yes, HVMlite (or however we will end up calling it) will allow these
> sorts of thing. But HVMlite is not supported yet at all. And it's x86
> only.
>
> -boris
>
>>
>>>   	else
>>>   		irq = irq_alloc_desc_at(gsi, -1);
>>> @@ -445,8 +445,8 @@ static void xen_free_irq(unsigned irq)
>>>
>>>   	kfree(info);
>>>
>>> -	/* Legacy IRQ descriptors are managed by the arch. */
>>> -	if (irq < NR_IRQS_LEGACY)
>>> +	/* On HVM legacy IRQ descriptors are managed by the arch. */
>>> +	if (xen_hvm_domain() && irq < NR_IRQS_LEGACY)
>>>   		return;
>>>
>>>   	irq_free_desc(irq);

-- 
  Vitaly

  reply	other threads:[~2015-11-18 14:28 UTC|newest]

Thread overview: 24+ 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 15:38 ` David Vrabel
2015-11-17 16:24 ` Juergen Gross
2015-11-17 16:24 ` Juergen Gross
2015-11-18 11:16 ` Vitaly Kuznetsov
2015-11-18 11:16 ` [Xen-devel] " Vitaly Kuznetsov
2015-11-18 14:03   ` Boris Ostrovsky
2015-11-18 14:28     ` Vitaly Kuznetsov [this message]
2015-11-18 14:28     ` Vitaly Kuznetsov
2015-11-18 15:00       ` Boris Ostrovsky
2015-11-18 15:00       ` [Xen-devel] " Boris Ostrovsky
2015-11-18 14:03   ` Boris Ostrovsky
  -- strict thread matches above, loose matches on Subject: below --
2015-11-20 16:25 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-20 16:25 Boris Ostrovsky
2015-11-17 15:36 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='87d1v7v0t8.fsf__25444.1839679659$1447857032$gmane$org@vitty.brq.redhat.com' \
    --to=vkuznets@redhat.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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.