From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Dexuan Cui <decui@microsoft.com>
Cc: Jeffrey Hugo <quic_jhugo@quicinc.com>,
"wei.liu@kernel.org" <wei.liu@kernel.org>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Michael Kelley (LINUX)" <mikelley@microsoft.com>,
"robh@kernel.org" <robh@kernel.org>,
"kw@linux.com" <kw@linux.com>,
"helgaas@kernel.org" <helgaas@kernel.org>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"boqun.feng@gmail.com" <boqun.feng@gmail.com>,
Boqun Feng <Boqun.Feng@microsoft.com>,
Carl Vanderlip <quic_carlv@quicinc.com>
Subject: Re: [PATCH] PCI: hv: Only reuse existing IRTE allocation for Multi-MSI
Date: Tue, 16 Aug 2022 17:47:32 +0200 [thread overview]
Message-ID: <Yvu8FJfWkWX3rhO5@lpieralisi> (raw)
In-Reply-To: <SA1PR21MB1335D9CF9F0B1C101F15E047BF659@SA1PR21MB1335.namprd21.prod.outlook.com>
On Wed, Aug 10, 2022 at 09:51:23PM +0000, Dexuan Cui wrote:
> > From: Jeffrey Hugo <quic_jhugo@quicinc.com>
> > Sent: Thursday, August 4, 2022 7:22 AM
> > ...
> > > Fixes: b4b77778ecc5 ("PCI: hv: Reuse existing IRTE allocation in
> > compose_msi_msg()")
> > > Signed-off-by: Dexuan Cui <decui@microsoft.com>
> > > Cc: Jeffrey Hugo <quic_jhugo@quicinc.com>
> > > Cc: Carl Vanderlip <quic_carlv@quicinc.com>
> > > ---
> >
> > I'm sorry a regression has been discovered. Right now, the issue
> > doesn't make sense to me. I'd love to know what you find out.
> >
> > This stopgap solution appears reasonable to me.
> >
> > Reviewed-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
>
> Hi Lorenzo, Bjorn and all,
> Would you please take a look at the patch?
I am not very happy with this patch, it is a temporary solution to
a potential problem (or reworded: we don't know what the problem is
but we are fixing it anyway - in a way that is potentially not
related to the bug at all).
If the commit you are fixing is the problem I'd rather revert it,
waiting to understand the problem and to rework the code accordingly.
I don't think b4b77778ecc5 is essential to Hyper-V code - it is a
rework, let's fix it and repost it when it is updated through the
debugging you are carrying out. In the meantime we can revert it
to fix the issue.
Thanks,
Lorenzo
next prev parent reply other threads:[~2022-08-16 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 2:51 [PATCH] PCI: hv: Only reuse existing IRTE allocation for Multi-MSI Dexuan Cui
2022-08-04 14:22 ` Jeffrey Hugo
2022-08-10 21:51 ` Dexuan Cui
2022-08-16 15:47 ` Lorenzo Pieralisi [this message]
2022-08-16 21:04 ` Dexuan Cui
2022-08-16 15:51 ` Bjorn Helgaas
2022-08-16 21:13 ` Dexuan Cui
2022-08-17 7:51 ` Lorenzo Pieralisi
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=Yvu8FJfWkWX3rhO5@lpieralisi \
--to=lpieralisi@kernel.org \
--cc=Boqun.Feng@microsoft.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=boqun.feng@gmail.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=helgaas@kernel.org \
--cc=kw@linux.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=quic_carlv@quicinc.com \
--cc=quic_jhugo@quicinc.com \
--cc=robh@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=wei.liu@kernel.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