All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "jeremy@goop.org" <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH] xen: do not unmask disabled IRQ on 	 eoi.
Date: Fri, 22 Oct 2010 09:07:16 +0100	[thread overview]
Message-ID: <1287734836.29224.648.camel@localhost.localdomain> (raw)
In-Reply-To: <4CC15C5B020000780001E8B2@vpn.id2.novell.com>

On Fri, 2010-10-22 at 08:41 +0100, Jan Beulich wrote: 
> >>> On 21.10.10 at 15:36, Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:
> > --- a/drivers/xen/events.c
> > +++ b/drivers/xen/events.c
> > @@ -436,21 +436,50 @@ static bool identity_mapped_irq(unsigned irq)
> >  	return irq < get_nr_hw_irqs();
> >  }
> >  
> > -static void pirq_eoi(unsigned int irq)
> > +static void eoi_pirq(unsigned int irq)
> >  {
> >  	struct irq_info *info = info_for_irq(irq);
> >  	struct physdev_eoi eoi = { .irq = info->u.pirq.gsi };
> > -	bool need_eoi;
> > +	int evtchn = evtchn_from_irq(irq);
> > +	int rc = 0, need_mask = 0;
> > +	struct shared_info *s = HYPERVISOR_shared_info;
> >  
> > -	need_eoi = pirq_needs_eoi(irq);
> > +	if (!VALID_EVTCHN(evtchn))
> > +		return;
> >  
> > -	if (!need_eoi || !pirq_eoi_does_unmask)
> > -		unmask_evtchn(info->evtchn);
> > +	move_masked_irq(irq);
> 
> It's not clear whether calling this function is valid when the IRQ isn't
> really masked.
> 
> In any case I'd suggest adding an IRQ_DISABLED check matching
> move_native_irq()'s.

Why not just call move_native_irq instead of move_masked_irq as
appropriate?

Ian.

  reply	other threads:[~2010-10-22  8:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-15 10:52 [PATCH] xen: do not unmask disabled IRQ on eoi Ian Campbell
2010-10-15 16:12 ` Stefano Stabellini
2010-10-15 16:32   ` Ian Campbell
2010-10-15 16:39     ` Ian Campbell
2010-10-15 17:03       ` Stefano Stabellini
2010-10-15 17:33         ` Jeremy Fitzhardinge
2010-10-18  8:09         ` Jan Beulich
2010-10-18 14:58           ` Stefano Stabellini
2010-10-18 15:16             ` Jan Beulich
2010-10-18 18:14               ` Stefano Stabellini
2010-10-18 20:04                 ` Stefano Stabellini
2010-10-19  7:13                   ` Jan Beulich
2010-10-19  6:36                 ` Jan Beulich
2010-10-21 13:36                   ` Stefano Stabellini
2010-10-22  7:41                     ` Jan Beulich
2010-10-22  8:07                       ` Ian Campbell [this message]
2010-10-22  8:29                         ` Jan Beulich
2010-10-22  8:34                           ` Ian Campbell
2010-10-22 13:57                             ` Stefano Stabellini
2010-10-22 14:48                               ` Jan Beulich
2010-10-22 16:24                                 ` Stefano Stabellini
2010-10-29 14:32                                   ` Stefano Stabellini
2010-10-22 12:04                       ` Stefano Stabellini

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=1287734836.29224.648.camel@localhost.localdomain \
    --to=ian.campbell@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    /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.