From: Anoob Soman <anoob.soman@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xenproject.org
Cc: jgross@suse.com
Subject: Re: xen-evtchn: Bind dyn evtchn:qemu-dm interrupt to next online CPU
Date: Wed, 31 May 2017 14:12:04 +0100 [thread overview]
Message-ID: <2395bd48-af76-53c4-0f16-c23269abe95e@citrix.com> (raw)
In-Reply-To: <993b26b9-d4cb-63dd-e39b-e2f5e5cd6246@oracle.com>
On 30/05/17 18:42, Boris Ostrovsky wrote:
> This is not worth API change so I guess we are going to have to use
> separate calls, as you originally proposed.
Sure. I will stick to making two hypercalls.
>> Do we need to look at IRQ affinity mask, if we are going to bind
>> eventchannel to smp_processor_id(). If we definitely need to use IRQ
>> affinity then binding to smp_processor_id() might not be the correct
>> approach.
> What if, for whatever reason, the current processor is not in the
> affinity mask of the IRQ?
Yes, there is a possibility of that happening, but chances are really
slim. I will drop the idea of binding evtchn to smp_processor_id and
instead change the logic to use a per_cpu(int) to hold last used cpu and
then use cpu_next_and(last_cpu, affinity, cpu_online_mask) to get next cpu.
-Anoob
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-05-31 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 17:15 xen-evtchn: Bind dyn evtchn:qemu-dm interrupt to next online CPU Anoob Soman
2017-05-16 19:02 ` Boris Ostrovsky
2017-05-17 15:28 ` Anoob Soman
2017-05-17 16:44 ` Boris Ostrovsky
2017-05-30 15:17 ` Anoob Soman
2017-05-30 17:42 ` Boris Ostrovsky
2017-05-31 13:12 ` Anoob Soman [this message]
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=2395bd48-af76-53c4-0f16-c23269abe95e@citrix.com \
--to=anoob.soman@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).