From: wanghuiqiang <wanghuiqiang@huawei.com> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>, "'Ard Biesheuvel'" <ardb@kernel.org> Cc: 'Marc Zyngier' <maz@kernel.org>, "'eric.auger@redhat.com'" <eric.auger@redhat.com>, "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>, "'linux-arm-kernel@lists.infradead.org'" <linux-arm-kernel@lists.infradead.org>, Linuxarm <linuxarm@huawei.com>, "xuwei (O)" <xuwei5@huawei.com> Subject: 答复: [PATCH] irqchip/gic-v3: Check SRE bit for GICv2 legacy support Date: Wed, 6 Jan 2021 09:22:18 +0000 [thread overview] Message-ID: <07084A11A8AB5A40A40B0218FE6F1CCA0F5B3322@dggeml510-mbx.china.huawei.com> (raw) In-Reply-To: <07084A11A8AB5A40A40B0218FE6F1CCA0F59630F@dggeml510-mbx.china.huawei.com> Hi Ard and all, The issue is root caused, it is introduced by BIOS new feature implemented. With old BIOS,we use static MADT table and the GICV/GICH is set to 0 and reported this table to OS. But we added new features which will dynamic update MADT table based on some external input, the developer is set GICV/GICH as what we have done like previous generation chipset code did. But in fact, there is different compared with old generation chipset code. I'll let my internal team know this and fix this issue in later BIOS release. Thanks! -----邮件原件----- 发件人: wanghuiqiang 发送时间: 2020年12月15日 15:49 收件人: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>; Ard Biesheuvel <ardb@kernel.org> 抄送: Marc Zyngier <maz@kernel.org>; eric.auger@redhat.com; linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; Linuxarm <linuxarm@huawei.com>; xuwei (O) <xuwei5@huawei.com> 主题: 答复: [PATCH] irqchip/gic-v3: Check SRE bit for GICv2 legacy support Sorry response late. Hi Shameer & Ard, Could you let me know which firmware you are using? If the difference is Madt table vGIC your pointed , they are the same. We changed the vGIC memory base address at very early design stage. Thanks! -----邮件原件----- 发件人: Shameerali Kolothum Thodi 发送时间: 2020年12月2日 16:23 收件人: Ard Biesheuvel <ardb@kernel.org> 抄送: Marc Zyngier <maz@kernel.org>; eric.auger@redhat.com; linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; Linuxarm <linuxarm@huawei.com>; wanghuiqiang <wanghuiqiang@huawei.com>; xuwei (O) <xuwei5@huawei.com> 主题: RE: [PATCH] irqchip/gic-v3: Check SRE bit for GICv2 legacy support [+] > -----Original Message----- > From: Ard Biesheuvel [mailto:ardb@kernel.org] > Sent: 30 November 2020 18:32 > To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com> > Cc: Marc Zyngier <maz@kernel.org>; eric.auger@redhat.com; > linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; > Linuxarm <linuxarm@huawei.com> > Subject: Re: [PATCH] irqchip/gic-v3: Check SRE bit for GICv2 legacy > support > ... > > Any clue why production D06 firmware deviates from the D06 port that > exists in Tianocore's edk2-platforms repository? Because that version > does not have this bug, and I wonder why that code was upstreamed at > all if a substantially different version gets shipped with production > hardware. Ok. Thanks for pointing this out. I have informed our UEFI team about this. They will check Internally and clarify. Regards, Shameer
WARNING: multiple messages have this Message-ID (diff)
From: wanghuiqiang <wanghuiqiang@huawei.com> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>, "'Ard Biesheuvel'" <ardb@kernel.org> Cc: 'Marc Zyngier' <maz@kernel.org>, Linuxarm <linuxarm@huawei.com>, "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>, "'eric.auger@redhat.com'" <eric.auger@redhat.com>, "xuwei \(O\)" <xuwei5@huawei.com>, "'linux-arm-kernel@lists.infradead.org'" <linux-arm-kernel@lists.infradead.org> Subject: 答复: [PATCH] irqchip/gic-v3: Check SRE bit for GICv2 legacy support Date: Wed, 6 Jan 2021 09:22:18 +0000 [thread overview] Message-ID: <07084A11A8AB5A40A40B0218FE6F1CCA0F5B3322@dggeml510-mbx.china.huawei.com> (raw) In-Reply-To: <07084A11A8AB5A40A40B0218FE6F1CCA0F59630F@dggeml510-mbx.china.huawei.com> Hi Ard and all, The issue is root caused, it is introduced by BIOS new feature implemented. With old BIOS,we use static MADT table and the GICV/GICH is set to 0 and reported this table to OS. But we added new features which will dynamic update MADT table based on some external input, the developer is set GICV/GICH as what we have done like previous generation chipset code did. But in fact, there is different compared with old generation chipset code. I'll let my internal team know this and fix this issue in later BIOS release. Thanks! -----邮件原件----- 发件人: wanghuiqiang 发送时间: 2020年12月15日 15:49 收件人: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>; Ard Biesheuvel <ardb@kernel.org> 抄送: Marc Zyngier <maz@kernel.org>; eric.auger@redhat.com; linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; Linuxarm <linuxarm@huawei.com>; xuwei (O) <xuwei5@huawei.com> 主题: 答复: [PATCH] irqchip/gic-v3: Check SRE bit for GICv2 legacy support Sorry response late. Hi Shameer & Ard, Could you let me know which firmware you are using? If the difference is Madt table vGIC your pointed , they are the same. We changed the vGIC memory base address at very early design stage. Thanks! -----邮件原件----- 发件人: Shameerali Kolothum Thodi 发送时间: 2020年12月2日 16:23 收件人: Ard Biesheuvel <ardb@kernel.org> 抄送: Marc Zyngier <maz@kernel.org>; eric.auger@redhat.com; linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; Linuxarm <linuxarm@huawei.com>; wanghuiqiang <wanghuiqiang@huawei.com>; xuwei (O) <xuwei5@huawei.com> 主题: RE: [PATCH] irqchip/gic-v3: Check SRE bit for GICv2 legacy support [+] > -----Original Message----- > From: Ard Biesheuvel [mailto:ardb@kernel.org] > Sent: 30 November 2020 18:32 > To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com> > Cc: Marc Zyngier <maz@kernel.org>; eric.auger@redhat.com; > linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; > Linuxarm <linuxarm@huawei.com> > Subject: Re: [PATCH] irqchip/gic-v3: Check SRE bit for GICv2 legacy > support > ... > > Any clue why production D06 firmware deviates from the D06 port that > exists in Tianocore's edk2-platforms repository? Because that version > does not have this bug, and I wonder why that code was upstreamed at > all if a substantially different version gets shipped with production > hardware. Ok. Thanks for pointing this out. I have informed our UEFI team about this. They will check Internally and clarify. Regards, Shameer _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-06 9:23 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-30 10:26 [PATCH] irqchip/gic-v3: Check SRE bit for GICv2 legacy support Shameer Kolothum 2020-11-30 10:26 ` Shameer Kolothum 2020-11-30 11:50 ` Zenghui Yu 2020-11-30 11:50 ` Zenghui Yu 2020-11-30 12:06 ` Shameerali Kolothum Thodi 2020-11-30 12:06 ` Shameerali Kolothum Thodi 2020-11-30 13:16 ` Marc Zyngier 2020-11-30 13:16 ` Marc Zyngier 2020-11-30 12:28 ` Marc Zyngier 2020-11-30 12:28 ` Marc Zyngier 2020-11-30 13:55 ` Shameerali Kolothum Thodi 2020-11-30 13:55 ` Shameerali Kolothum Thodi 2020-11-30 14:56 ` Marc Zyngier 2020-11-30 14:56 ` Marc Zyngier 2020-11-30 16:20 ` Shameerali Kolothum Thodi 2020-11-30 16:20 ` Shameerali Kolothum Thodi 2020-11-30 18:31 ` Ard Biesheuvel 2020-11-30 18:31 ` Ard Biesheuvel 2020-12-02 8:23 ` Shameerali Kolothum Thodi 2020-12-02 8:23 ` Shameerali Kolothum Thodi 2020-12-15 7:49 ` 答复: " wanghuiqiang 2020-12-15 7:49 ` wanghuiqiang 2020-12-15 10:00 ` Shameerali Kolothum Thodi 2020-12-15 10:00 ` Shameerali Kolothum Thodi 2021-01-06 9:22 ` wanghuiqiang [this message] 2021-01-06 9:22 ` 答复: " wanghuiqiang 2021-01-07 14:42 ` Shameerali Kolothum Thodi 2021-01-07 14:42 ` Shameerali Kolothum Thodi
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=07084A11A8AB5A40A40B0218FE6F1CCA0F5B3322@dggeml510-mbx.china.huawei.com \ --to=wanghuiqiang@huawei.com \ --cc=ardb@kernel.org \ --cc=eric.auger@redhat.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxarm@huawei.com \ --cc=maz@kernel.org \ --cc=shameerali.kolothum.thodi@huawei.com \ --cc=xuwei5@huawei.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.