xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>,
	Jan Beulich <JBeulich@suse.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PVH]: Help: msi.c
Date: Fri, 14 Dec 2012 12:08:36 -0800	[thread overview]
Message-ID: <20121214120836.6ec4ad4a@mantra.us.oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1212131409040.17523@kaball.uk.xensource.com>

On Thu, 13 Dec 2012 14:25:16 +0000
Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:

> On Thu, 13 Dec 2012, Jan Beulich wrote:
> > >>> On 13.12.12 at 13:19, Stefano Stabellini
> > >>> <stefano.stabellini@eu.citrix.com>
> > wrote:
> > > On Thu, 13 Dec 2012, Jan Beulich wrote:
> > >> >>> On 13.12.12 at 02:43, Mukesh Rathor
> > >> >>> <mukesh.rathor@oracle.com> wrote:
> 
> Actually I think that you might be right: just looking at the code it
> seems that the mask bits get written to the table once as part of the
> initialization process:
> 
> pci_enable_msix -> msix_capability_init -> msix_program_entries
> 
> Unfortunately msix_program_entries is called few lines after
> arch_setup_msi_irqs, where we call PHYSDEVOP_map_pirq to map the MSI
> as a pirq.
> However after that is done, all the masking/unmask is done via
> irq_mask that we handle properly masking/unmasking the corresponding
> event channels.
> 
> 
> Possible solutions on top of my head:
> 
> - in msix_program_entries instead of writing to the table directly
> (__msix_mask_irq), call desc->irq_data.chip->irq_mask(); 
> 
> - replace msix_program_entries with arch_msix_program_entries, but it
> would probably be unpopular.


Can you or Jan or somebody please take that over? I can focus on other
PVH things then and try to get a patch in asap.

Thanks,
Mukesh

  reply	other threads:[~2012-12-14 20:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-08  1:46 [PVH]: Help: msi.c Mukesh Rathor
2012-12-10  9:43 ` Jan Beulich
2012-12-11  2:43   ` Mukesh Rathor
2012-12-11 12:10     ` Stefano Stabellini
2012-12-13  1:15       ` Mukesh Rathor
2012-12-13  1:43         ` Mukesh Rathor
2012-12-13 10:42           ` Jan Beulich
2012-12-13 12:19             ` Stefano Stabellini
2012-12-13 13:39               ` Jan Beulich
2012-12-13 14:25                 ` Stefano Stabellini
2012-12-14 20:08                   ` Mukesh Rathor [this message]
2012-12-17 12:42                     ` Stefano Stabellini
2012-12-17 12:57                       ` Jan Beulich
2012-12-17 14:16                         ` Stefano Stabellini
2012-12-17 15:28                           ` Jan Beulich
2012-12-18 21:16                   ` Konrad Rzeszutek Wilk
2012-12-19 11:19                     ` Stefano Stabellini
2012-12-19 15:37                       ` Konrad Rzeszutek Wilk
2012-12-20 11:49                         ` Stefano Stabellini
2012-12-21 21:01                           ` Konrad Rzeszutek Wilk
2013-01-04 16:57                             ` Stefano Stabellini
2013-01-08 19:49                               ` Konrad Rzeszutek Wilk

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=20121214120836.6ec4ad4a@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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 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).