[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1692862032-37839-1-git-send-email-huangshaobo3@xiaomi.com>
Date: Thu, 24 Aug 2023 00:27:12 -0700
From: <huangshaobo3@...omi.com>
To: <tglx@...utronix.de>
CC: <bhelgaas@...gle.com>, <chenwei29@...omi.com>,
<darwi@...utronix.de>, <huangshaobo3@...omi.com>, <jgg@...pe.ca>,
<kevin.tian@...el.com>, <linux-kernel@...r.kernel.org>,
<linux-pci@...r.kernel.org>, <weipengliang@...omi.com>,
<wengjinfei@...omi.com>
Subject: Re: Subject: [PATCH] pci/msi: remove redundant calculation in msi_setup_msi_desc
On Wed, 23 Aug 2023 16:15:27 +0200, Thomas Gleixner wrote:
> On Fri, Aug 18 2023 at 07:26, 黄少波 wrote:
> Your patch is corrupt:
> Applying: Subject: [PATCH] pci/msi: remove redundant calculation in msi_setup_msi_desc
> error: corrupt patch at line 12
> It's DOS mangled and whitespace damaged.
Very sorry, may have accidentally broken the patch format,
and will make sure to use plain text next time.
> > Whether to support 64-bit address status has been calculated before,
> > and the calculation result can be used directly afterwards, so use
> > msi_attrib.is_64 to avoid double calculation.
> I'm not seeing what this solves:
> > - if (control & PCI_MSI_FLAGS_64BIT)
> > + if (desc.pci.msi_attrib.is_64)
> Both variants resolve to a test of a bit and a conditional instruction
> on the result. It's exactly zero difference in terms of "calculation".
> So all this does is change the memory location to test. Not more not
> less. It does not generate better code and does not save anything.
It may not be appropriate to write to eliminate duplicate calculations,
can it be proposed again with clean code?
> Thanks,
> tglx
thanks,
sparkhuang
#/******本邮件及其附件含有小米公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件! This e-mail and its attachments contain confidential information from XIAOMI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!******/#
Powered by blists - more mailing lists