[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <835eae02-3f7b-42b8-b237-437699c8103f@huawei.com>
Date: Sat, 2 Aug 2025 11:05:55 +0800
From: Jinqian Yang <yangjinqian1@...wei.com>
To: Marc Zyngier <maz@...nel.org>
CC: <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
Zhou Wang <wangzhou1@...ilicon.com>, jiangkunkun <jiangkunkun@...wei.com>,
Luchunhua <luchunhua@...wei.com>, liuyonglong <liuyonglong@...wei.com>,
"xuwei (O)" <xuwei5@...wei.com>, "Zengtao (B)" <prime.zeng@...ilicon.com>
Subject: Re: Regarding the Issue of vNMI Not Supporting Live Migration
On 2025/8/1 20:07, Marc Zyngier wrote:
> On Fri, 01 Aug 2025 09:00:07 +0100,
> Jinqian Yang <yangjinqian1@...wei.com> wrote:
>>
>> Hi,marc
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=arm64/nmi
>>
>> During the testing of this set of vNMI patches, it was discovered that
>> vNMI do not support live
>> migration. The reason is that GICD_INMIR/GICR_INMIR0 have not been
>> migrated, causing
>> irq->nmi to reset to 0 after migration. Therefore, to resolve this
>> issue, we need to complete the
>> migration of GICD_INMIR/GICR_INMIR0. This set of patches does not seem
>> to have been uploaded
>> to the mainline. I was wondering if these are scheduled for upload to
>> the mainline?
>
> There patches are *dead*, and will *not* be upstreamed as such. You
> can tell from the date and the base commit that they are old and
> unmaintained.
>
> Please do not pick random branches from my tree.
>
> Thanks,
>
> M.
>
Noted with thanks — will avoid referencing outdated branches in the future.
Thanks,
Jinqian
Powered by blists - more mailing lists