From: Marc Zyngier <maz@kernel.org>
To: Kunkun Jiang <jiangkunkun@huawei.com>
Cc: Eric Auger <eauger@redhat.com>,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
<linux-arm-kernel@lists.infradead.org>, <kvmarm@lists.linux.dev>,
<wanghaibin.wang@huawei.com>, <lishusen2@huawei.com>
Subject: Re: [PATCH] KVM: arm64: vgic-its: clear dte when mapd unmaps a device
Date: Thu, 20 Jun 2024 14:58:35 +0100 [thread overview]
Message-ID: <864j9nk96c.wl-maz@kernel.org> (raw)
In-Reply-To: <480900e7-4894-4fc9-5671-f29523f2672a@huawei.com>
On Thu, 20 Jun 2024 14:32:20 +0100,
Kunkun Jiang <jiangkunkun@huawei.com> wrote:
>
> Hi Eric,
>
> On 2024/6/19 1:18, Eric Auger wrote:
> >> Also, is the device table the only one that is subject to this
> >> 'reload' problem? How about the Collection table?
> > The collection table is not indexed by the collection ID and when saving
> > we end up writing an invalid dummy entry to close the recording. So I
> > don't think we have the same problem there.
> I'm a little confused here. In the current Linux, there is no implementation
> of mapc unmaps a cte. But should this scenario be considered in
> vgic-its?
We implement the "HW", not what Linux does.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-06-20 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 9:38 [PATCH] KVM: arm64: vgic-its: clear dte when mapd unmaps a device Kunkun Jiang
2024-06-13 14:44 ` Marc Zyngier
2024-06-18 17:18 ` Eric Auger
2024-06-20 13:32 ` Kunkun Jiang
2024-06-20 13:58 ` Marc Zyngier [this message]
2024-06-20 13:18 ` Kunkun Jiang
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=864j9nk96c.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=eauger@redhat.com \
--cc=james.morse@arm.com \
--cc=jiangkunkun@huawei.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lishusen2@huawei.com \
--cc=oliver.upton@linux.dev \
--cc=rdunlap@infradead.org \
--cc=suzuki.poulose@arm.com \
--cc=wanghaibin.wang@huawei.com \
--cc=will@kernel.org \
--cc=yuzenghui@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox