All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Jinqian Yang <yangjinqian1@huawei.com>
Cc: <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Zhou Wang <wangzhou1@hisilicon.com>,
	jiangkunkun <jiangkunkun@huawei.com>,
	Luchunhua <luchunhua@huawei.com>,
	liuyonglong <liuyonglong@huawei.com>,
	"xuwei (O)" <xuwei5@huawei.com>,
	"Zengtao (B)" <prime.zeng@hisilicon.com>
Subject: Re: Regarding the Issue of vNMI Not Supporting Live Migration
Date: Fri, 01 Aug 2025 13:07:17 +0100	[thread overview]
Message-ID: <86wm7n6ya2.wl-maz@kernel.org> (raw)
In-Reply-To: <c7bc0979-3721-49ba-89bd-ebcaa5ce70d9@huawei.com>

On Fri, 01 Aug 2025 09:00:07 +0100,
Jinqian Yang <yangjinqian1@huawei.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.

-- 
Without deviation from the norm, progress is not possible.


  reply	other threads:[~2025-08-01 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-01  8:00 Regarding the Issue of vNMI Not Supporting Live Migration Jinqian Yang
2025-08-01 12:07 ` Marc Zyngier [this message]
2025-08-02  3:05   ` Jinqian Yang

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=86wm7n6ya2.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=jiangkunkun@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuyonglong@huawei.com \
    --cc=luchunhua@huawei.com \
    --cc=prime.zeng@hisilicon.com \
    --cc=wangzhou1@hisilicon.com \
    --cc=xuwei5@huawei.com \
    --cc=yangjinqian1@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: link
Be 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.