From: Vitaly Chikunov <vt@altlinux.org>
To: "Michael Kelley (LINUX)" <mikelley@microsoft.com>
Cc: "linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Tianyu Lan <Tianyu.Lan@microsoft.com>,
Long Li <longli@microsoft.com>,
"Dmitry V. Levin" <ldv@altlinux.org>
Subject: Re: [PATCH] drivers: hv: vmbus: Fix build on GCC 11 failed by DMA_BIT_MASK(64) expansion
Date: Fri, 4 Feb 2022 05:03:43 +0300 [thread overview]
Message-ID: <20220204020343.5uxbhkwcux4cya77@altlinux.org> (raw)
In-Reply-To: <MWHPR21MB15936A0F46747D81D3CBCC12D7299@MWHPR21MB1593.namprd21.prod.outlook.com>
Michael,
On Fri, Feb 04, 2022 at 01:48:32AM +0000, Michael Kelley (LINUX) wrote:
> From: Vitaly Chikunov <vt@altlinux.org> Sent: Thursday, February 3, 2022 4:58 PM
> >
> > GCC 11.2.1 cannot understand that value 64 is excluded from the shift
> > at compile time resulting in build error[1]:
> >
> > drivers/hv/vmbus_drv.c:2082:29: error: shift count >= width of type [-Werror,-
> > Wshift-count-overflow]
> > static u64 vmbus_dma_mask = DMA_BIT_MASK(64);
> > ^~~~~~~~~~~~~~~~
> > ./include/linux/dma-mapping.h:76:54: note: expanded from macro 'DMA_BIT_MASK'
> > #define DMA_BIT_MASK(n) (((n) == 64) ? ~0ULL : ((1ULL<<(n))-1))
> > ^ ~~~
> >
> > Avoid using DMA_BIT_MASK macro for that corner case.
>
> If we need a temporary hack to solve the build problem, I can live with
> that. But I see 230 other places in kernel code where DMA_BIT_MASK(64)
> is used, so I'm wondering if this particular hack is effective. We need a
> more comprehensive solution that fixes the definition of
> DMA_BIT_MASK() so it will work with a constant '64' as the parameter.
Ah, I suddenly realised that this build was using Clang 12.0.1, not GCC
11. So my patch description is wrong!
Thanks,
>
> Michael
>
> >
> > Cc: Tianyu Lan <Tianyu.Lan@microsoft.com>
> > Cc: Michael Kelley <mikelley@microsoft.com>
> > Cc: Long Li <longli@microsoft.com>
> > Cc: Wei Liu <wei.liu@kernel.org>
> > Link: https://lore.kernel.org/linux-hyperv/20220203235828.hcsj6najsl7yxmxa@altlinux.org/
> > Signed-off-by: Vitaly Chikunov <vt@altlinux.org>
> > ---
> > drivers/hv/vmbus_drv.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> > index 17bf55fe3169..2376ee484362 100644
> > --- a/drivers/hv/vmbus_drv.c
> > +++ b/drivers/hv/vmbus_drv.c
> > @@ -2079,7 +2079,7 @@ struct hv_device *vmbus_device_create(const guid_t *type,
> > return child_device_obj;
> > }
> >
> > -static u64 vmbus_dma_mask = DMA_BIT_MASK(64);
> > +static u64 vmbus_dma_mask = ~0ULL;
> > /*
> > * vmbus_device_register - Register the child device
> > */
> > --
> > 2.33.0
prev parent reply other threads:[~2022-02-04 2:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 0:57 [PATCH] drivers: hv: vmbus: Fix build on GCC 11 failed by DMA_BIT_MASK(64) expansion Vitaly Chikunov
2022-02-04 1:48 ` Michael Kelley (LINUX)
2022-02-04 1:54 ` Vitaly Chikunov
2022-02-04 2:03 ` Vitaly Chikunov [this message]
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=20220204020343.5uxbhkwcux4cya77@altlinux.org \
--to=vt@altlinux.org \
--cc=Tianyu.Lan@microsoft.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=ldv@altlinux.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mikelley@microsoft.com \
--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