From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Zhenzhong Duan <zhenzhong.duan@oracle.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
xen-devel@lists.xenproject.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Sucheta Chakraborty <sucheta.chakraborty@qlogic.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH] PCI: Introduce two new MSI infrastructure calls for masking/unmasking.
Date: Fri, 8 Nov 2013 10:35:07 -0500 [thread overview]
Message-ID: <20131108153507.GA24755@phenom.dumpdata.com> (raw)
In-Reply-To: <527C41E9.6040002@oracle.com>
On Fri, Nov 08, 2013 at 09:44:09AM +0800, Zhenzhong Duan wrote:
>
> On 2013-11-07 07:51, Bjorn Helgaas wrote:
> >[+cc Thomas, Ingo, Peter, x86 list]
> >
> >On Wed, Nov 6, 2013 at 2:16 PM, Konrad Rzeszutek Wilk
> ><konrad.wilk@oracle.com> wrote:
> >>Certain platforms do not allow writes in the MSI-X bars
> >>to setup or tear down vector values. To combat against
> >>the generic code trying to write to that and either silently
> >>being ignored or crashing due to the pagetables being marked r/o
> >>this patch introduces a platform over-write.
> >>
> >>Note that we keep two separate, non-weak, functions
> >>default_mask_msi_irqs() and default_mask_msix_irqs() for the
> >>behavior of the arch_mask_msi_irqs() and arch_mask_msix_irqs(),
> >>as the default behavior is needed by x86 PCI code.
> >>
> >>For Xen, which does not allow the guest to write to MSI-X
> >>tables - as the hypervisor is solely responsible for setting
> >>the vector values - we implement two nops.
> >>
> >>CC: Bjorn Helgaas <bhelgaas@google.com>
> >>CC: Sucheta Chakraborty <sucheta.chakraborty@qlogic.com>
> >>CC: Zhenzhong Duan <zhenzhong.duan@oracle.com>
> >>Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> >I think this is safe, and I'd like to squeeze it into the v3.13 merge
> >window next week, since it supersedes three patches Zhenzhong has been
> >trying to get in since July [1], and this patch is much simpler to
> >understand.
> This patch could replace the first two.
> I think the third patch of mine is still needed as it does a
> different thing.
> It optimizes restore path in dom0.
I tried to rebase it on top of this patch but it ended up that
you still need the two arguments (for restore_... operation).
But perhaps there is a better way. If you can rebase on top
of this patch - and send it out - that would be great!
next prev parent reply other threads:[~2013-11-08 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 21:16 [PATCH] PCI: Introduce two new MSI infrastructure calls for masking/unmasking Konrad Rzeszutek Wilk
2013-11-06 23:51 ` Bjorn Helgaas
2013-11-07 1:42 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-11-07 21:47 ` Bjorn Helgaas
2013-11-08 1:44 ` Zhenzhong Duan
2013-11-08 15:35 ` Konrad Rzeszutek Wilk [this message]
2013-12-04 4:57 ` DuanZhenzhong
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=20131108153507.GA24755@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=bhelgaas@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sucheta.chakraborty@qlogic.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=zhenzhong.duan@oracle.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 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).