All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>, konrad.wilk@oracle.com
Cc: xen-devel@lists.xenproject.org, annie.li@oracle.com,
	linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH 1/4] xen/events: Clear cpu_evtchn_mask before resuming
Date: Wed, 29 Apr 2015 14:26:53 -0400	[thread overview]
Message-ID: <5541226D.3070501@oracle.com> (raw)
In-Reply-To: <55411BEF.5050605@citrix.com>

On 04/29/2015 01:59 PM, David Vrabel wrote:
> On 29/04/15 17:54, Boris Ostrovsky wrote:
>> On 04/29/2015 12:32 PM, David Vrabel wrote:
>>> On 28/04/15 19:29, Boris Ostrovsky wrote:
>>>> On 04/28/2015 12:28 PM, David Vrabel wrote:
>>>>>    From the commit log the evtchn_2l_resume() fucntion that's added
>>>>> sounds
>>>>> like it fixes the problem on its own?
>>>> It in fact makes this problem worse since now that cpu_evtchn_mask is
>>>> cleared during resume we cannot process the interrupt anymore in
>>>> evtchn_2l_handle_events(): irqs have to be bound to a cpu in order for
>>>> an interrupt to be processed.
>>> Perhaps evtchn_2l_resume() should set the local cpu mask for any bound
>>> event channels? And then you wouldn't need IRQ_MOVE_PCNTX.
>> But then (at least in 2-level case) more than one VCPUs may pick the
>> same interrupt, won't they? Because the local cpu mask is what tells a
>> VCPU that it is allowed to claim an interrupt.
>
> We know that all event channels at this point are on VCPU0 (right?) so
> we only set the bit in that VCPU's mask.

This is pretty much what I was suggesting since setting the mask is done 
via bind_evtchn_to_cpu(). Except that I also want to call 
EVTCHNOP_bind_vcpu before that, just in case.

-boris

  parent reply	other threads:[~2015-04-29 18:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 15:52 [PATCH 0/4] A few event channel-related fixes Boris Ostrovsky
2015-04-28 15:52 ` [PATCH 1/4] xen/events: Clear cpu_evtchn_mask before resuming Boris Ostrovsky
2015-04-28 16:28   ` David Vrabel
2015-04-28 16:28   ` [Xen-devel] " David Vrabel
2015-04-28 18:29     ` Boris Ostrovsky
2015-04-29 16:32       ` David Vrabel
2015-04-29 16:32       ` [Xen-devel] " David Vrabel
2015-04-29 16:54         ` Boris Ostrovsky
2015-04-29 17:59           ` David Vrabel
2015-04-29 18:26             ` Boris Ostrovsky
2015-04-29 18:26             ` Boris Ostrovsky [this message]
2015-04-29 17:59           ` David Vrabel
2015-04-29 16:54         ` Boris Ostrovsky
2015-04-28 18:29     ` Boris Ostrovsky
2015-04-28 15:52 ` Boris Ostrovsky
2015-04-28 15:52 ` [PATCH 2/4] xen/xenbus: Update xenbus event channel on resume Boris Ostrovsky
2015-04-28 16:32   ` David Vrabel
2015-04-28 16:32   ` [Xen-devel] " David Vrabel
2015-04-28 15:52 ` Boris Ostrovsky
2015-04-28 15:52 ` [PATCH 3/4] xen/console: Update console " Boris Ostrovsky
2015-04-28 16:33   ` [Xen-devel] " David Vrabel
2015-04-28 16:33   ` David Vrabel
2015-04-28 15:52 ` Boris Ostrovsky
2015-04-28 15:52 ` [PATCH 4/4] xen/events: Set irq_info->evtchn before binding the channel to CPU in __startup_pirq() Boris Ostrovsky
2015-04-28 16:34   ` [Xen-devel] " David Vrabel
2015-04-28 16:34   ` David Vrabel
2015-04-28 15:52 ` 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=5541226D.3070501@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=annie.li@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.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 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.