From: Anoob Soman <anoob.soman@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Cc: <jgross@suse.com>
Subject: Re: [PATCH] xen-evtchn: Bind dyn evtchn:qemu-dm interrupt to next online VCPU
Date: Mon, 5 Jun 2017 11:14:42 +0100 [thread overview]
Message-ID: <5a5d9355-34fc-57aa-825c-81123f6bb74e@citrix.com> (raw)
In-Reply-To: <363cb97a-7dc1-ae4f-da93-30e7658cef00@oracle.com>
On 02/06/17 17:24, Boris Ostrovsky wrote:
>>
>> static int set_affinity_irq(struct irq_data *data, const struct cpumask *dest,
>> bool force)
>> diff --git a/drivers/xen/evtchn.c b/drivers/xen/evtchn.c
>> index 10f1ef5..1192f24 100644
>> --- a/drivers/xen/evtchn.c
>> +++ b/drivers/xen/evtchn.c
>> @@ -58,6 +58,8 @@
>> #include <xen/xen-ops.h>
>> #include <asm/xen/hypervisor.h>
>>
>> +static DEFINE_PER_CPU(int, bind_last_selected_cpu);
> This should be moved into evtchn_bind_interdom_next_vcpu() since that's
> the only place referencing it.
Sure, I will do it.
>
> Why is it a percpu variable BTW? Wouldn't making it global result in
> better interrupt distribution?
The reason for percpu instead of global, was to avoid locking. We can
have a global variable (last_cpu) without locking, but value of last_cpu
wont be consistent, without locks. Moreover, since irq_affinity is also
used in the calculation of cpu to bind, having a percpu or global
wouldn't really matter, as the result (selected_cpu) is more likely to
be random (because different irqs can have different affinity). What do
you guys suggest.
>
>> +
>> struct per_user_data {
>> struct mutex bind_mutex; /* serialize bind/unbind operations */
>> struct rb_root evtchns;
>> @@ -421,6 +423,36 @@ static void evtchn_unbind_from_user(struct per_user_data *u,
>> del_evtchn(u, evtchn);
>> }
>>
>> +static void evtchn_bind_interdom_next_vcpu(int evtchn)
>> +{
>> + unsigned int selected_cpu, irq;
>> + struct irq_desc *desc = NULL;
>> + unsigned long flags;
>> +
>> + irq = irq_from_evtchn(evtchn);
>> + desc = irq_to_desc(irq);
>> +
>> + if (!desc)
>> + return;
>> +
>> + raw_spin_lock_irqsave(&desc->lock, flags);
>> + selected_cpu = this_cpu_read(bind_last_selected_cpu);
>> + selected_cpu = cpumask_next_and(selected_cpu,
>> + desc->irq_common_data.affinity, cpu_online_mask);
>> +
>> + if (unlikely(selected_cpu >= nr_cpu_ids))
>> + selected_cpu = cpumask_first_and(desc->irq_common_data.affinity,
>> + cpu_online_mask);
>> +
>> + raw_spin_unlock_irqrestore(&desc->lock, flags);
> I think if you follow Juergen's suggestion of wrapping everything into
> irq_enable/disable you can drop the lock altogether (assuming you keep
> bind_last_selected_cpu percpu).
>
> -boris
>
I think we would still require spin_lock(). spin_lock is for irq_desc.
>> + this_cpu_write(bind_last_selected_cpu, selected_cpu);
>> +
>> + local_irq_disable();
>> + /* unmask expects irqs to be disabled */
>> + xen_rebind_evtchn_to_cpu(evtchn, selected_cpu);
>> + local_irq_enable();
>> +}
>> +
>>
next prev parent reply other threads:[~2017-06-05 10:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 14:49 Anoob Soman
2017-06-02 15:10 ` Juergen Gross
2017-06-05 9:54 ` Anoob Soman
2017-06-02 16:24 ` Boris Ostrovsky
2017-06-05 10:14 ` Anoob Soman [this message]
2017-06-05 14:10 ` Boris Ostrovsky
2017-06-05 14:49 ` [Xen-devel] " Anoob Soman
2017-06-05 15:32 ` Boris Ostrovsky
2017-06-05 16:14 ` Anoob Soman
2017-06-05 16:46 ` Boris Ostrovsky
2017-06-05 17:13 ` Anoob Soman
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=5a5d9355-34fc-57aa-825c-81123f6bb74e@citrix.com \
--to=anoob.soman@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®