From: Zenghui Yu <yuzenghui@huawei.com>
To: Marc Zyngier <maz@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<kvmarm@lists.cs.columbia.edu>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Jason Cooper <jason@lakedaemon.net>,
"Robert Richter" <rrichter@marvell.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Eric Auger" <eric.auger@redhat.com>,
James Morse <james.morse@arm.com>,
"Julien Thierry" <julien.thierry.kdev@gmail.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: Re: [PATCH v4 08/20] irqchip/gic-v4.1: Plumb get/set_irqchip_state SGI callbacks
Date: Wed, 19 Feb 2020 23:18:16 +0800 [thread overview]
Message-ID: <8c538d2e-5ec8-0fd0-8999-e43a847df4c1@huawei.com> (raw)
In-Reply-To: <8db95a86-0981-710b-6c82-be7f7f844151@huawei.com>
On 2020/2/19 19:50, Zenghui Yu wrote:
> 3. it looks like KVM makes the assumption that the per-RD MMIO region
> will only be accessed by the associated VCPU? But I think this's not
> restricted by the architecture, we can do it better. Or I've just
> missed some important points here.
(After some basic tests, KVM actually does the right thing!)
So I must have some mis-understanding on this point, please
ignore it. I'll dig it further myself, sorry for the noisy.
Thanks,
Zenghui
WARNING: multiple messages have this Message-ID (diff)
From: Zenghui Yu <yuzenghui@huawei.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Jason Cooper <jason@lakedaemon.net>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Robert Richter <rrichter@marvell.com>,
Thomas Gleixner <tglx@linutronix.de>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 08/20] irqchip/gic-v4.1: Plumb get/set_irqchip_state SGI callbacks
Date: Wed, 19 Feb 2020 23:18:16 +0800 [thread overview]
Message-ID: <8c538d2e-5ec8-0fd0-8999-e43a847df4c1@huawei.com> (raw)
In-Reply-To: <8db95a86-0981-710b-6c82-be7f7f844151@huawei.com>
On 2020/2/19 19:50, Zenghui Yu wrote:
> 3. it looks like KVM makes the assumption that the per-RD MMIO region
> will only be accessed by the associated VCPU? But I think this's not
> restricted by the architecture, we can do it better. Or I've just
> missed some important points here.
(After some basic tests, KVM actually does the right thing!)
So I must have some mis-understanding on this point, please
ignore it. I'll dig it further myself, sorry for the noisy.
Thanks,
Zenghui
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Zenghui Yu <yuzenghui@huawei.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Jason Cooper <jason@lakedaemon.net>,
kvm@vger.kernel.org, Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-kernel@vger.kernel.org, Eric Auger <eric.auger@redhat.com>,
Robert Richter <rrichter@marvell.com>,
James Morse <james.morse@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 08/20] irqchip/gic-v4.1: Plumb get/set_irqchip_state SGI callbacks
Date: Wed, 19 Feb 2020 23:18:16 +0800 [thread overview]
Message-ID: <8c538d2e-5ec8-0fd0-8999-e43a847df4c1@huawei.com> (raw)
In-Reply-To: <8db95a86-0981-710b-6c82-be7f7f844151@huawei.com>
On 2020/2/19 19:50, Zenghui Yu wrote:
> 3. it looks like KVM makes the assumption that the per-RD MMIO region
> will only be accessed by the associated VCPU? But I think this's not
> restricted by the architecture, we can do it better. Or I've just
> missed some important points here.
(After some basic tests, KVM actually does the right thing!)
So I must have some mis-understanding on this point, please
ignore it. I'll dig it further myself, sorry for the noisy.
Thanks,
Zenghui
_______________________________________________
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:[~2020-02-19 15:18 UTC|newest]
Thread overview: 142+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 14:57 [PATCH v4 00/20] irqchip/gic-v4: GICv4.1 architecture support Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` [PATCH v4 01/20] irqchip/gic-v4.1: Skip absent CPUs while iterating over redistributors Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-17 9:11 ` Zenghui Yu
2020-02-17 9:11 ` Zenghui Yu
2020-02-17 9:11 ` Zenghui Yu
2020-02-14 14:57 ` [PATCH v4 02/20] irqchip/gic-v3: Use SGIs without active state if offered Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-17 9:18 ` Zenghui Yu
2020-02-17 9:18 ` Zenghui Yu
2020-02-17 9:18 ` Zenghui Yu
2020-02-14 14:57 ` [PATCH v4 03/20] irqchip/gic-v4.1: Advertise support v4.1 to KVM Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-17 9:09 ` Zenghui Yu
2020-02-17 9:09 ` Zenghui Yu
2020-02-17 9:09 ` Zenghui Yu
2020-02-14 14:57 ` [PATCH v4 04/20] irqchip/gic-v4.1: Map the ITS SGIR register page Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-20 3:17 ` Zenghui Yu
2020-02-20 3:17 ` Zenghui Yu
2020-02-20 3:17 ` Zenghui Yu
2020-02-14 14:57 ` [PATCH v4 05/20] irqchip/gic-v4.1: Plumb skeletal VSGI irqchip Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-20 3:21 ` Zenghui Yu
2020-02-20 3:21 ` Zenghui Yu
2020-02-20 3:21 ` Zenghui Yu
2020-02-14 14:57 ` [PATCH v4 06/20] irqchip/gic-v4.1: Add initial SGI configuration Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-18 7:25 ` Zenghui Yu
2020-02-18 7:25 ` Zenghui Yu
2020-02-18 7:25 ` Zenghui Yu
2020-02-18 9:46 ` Marc Zyngier
2020-02-18 9:46 ` Marc Zyngier
2020-02-18 9:46 ` Marc Zyngier
2020-02-20 3:25 ` Zenghui Yu
2020-02-20 3:25 ` Zenghui Yu
2020-02-20 3:25 ` Zenghui Yu
2020-02-14 14:57 ` [PATCH v4 07/20] irqchip/gic-v4.1: Plumb mask/unmask SGI callbacks Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-20 3:32 ` Zenghui Yu
2020-02-20 3:32 ` Zenghui Yu
2020-02-20 3:32 ` Zenghui Yu
2020-02-14 14:57 ` [PATCH v4 08/20] irqchip/gic-v4.1: Plumb get/set_irqchip_state " Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-18 7:00 ` Zenghui Yu
2020-02-18 7:00 ` Zenghui Yu
2020-02-18 7:00 ` Zenghui Yu
2020-02-18 9:27 ` Marc Zyngier
2020-02-18 9:27 ` Marc Zyngier
2020-02-18 9:27 ` Marc Zyngier
2020-02-18 15:31 ` Marc Zyngier
2020-02-18 15:31 ` Marc Zyngier
2020-02-18 15:31 ` Marc Zyngier
2020-02-19 11:50 ` Zenghui Yu
2020-02-19 11:50 ` Zenghui Yu
2020-02-19 11:50 ` Zenghui Yu
2020-02-19 15:18 ` Zenghui Yu [this message]
2020-02-19 15:18 ` Zenghui Yu
2020-02-19 15:18 ` Zenghui Yu
2020-02-20 3:11 ` Zenghui Yu
2020-02-20 3:11 ` Zenghui Yu
2020-02-20 3:11 ` Zenghui Yu
2020-02-28 19:37 ` Marc Zyngier
2020-02-28 19:37 ` Marc Zyngier
2020-02-28 19:37 ` Marc Zyngier
2020-03-01 19:00 ` Marc Zyngier
2020-03-01 19:00 ` Marc Zyngier
2020-03-01 19:00 ` Marc Zyngier
2020-03-02 8:18 ` Zenghui Yu
2020-03-02 8:18 ` Zenghui Yu
2020-03-02 8:18 ` Zenghui Yu
2020-03-02 12:09 ` Marc Zyngier
2020-03-02 12:09 ` Marc Zyngier
2020-03-02 12:09 ` Marc Zyngier
2020-03-02 14:21 ` Bill Barrow
2020-02-14 14:57 ` [PATCH v4 09/20] irqchip/gic-v4.1: Plumb set_vcpu_affinity " Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-20 3:37 ` Zenghui Yu
2020-02-20 3:37 ` Zenghui Yu
2020-02-20 3:37 ` Zenghui Yu
2020-02-28 19:00 ` Marc Zyngier
2020-02-28 19:00 ` Marc Zyngier
2020-02-28 19:00 ` Marc Zyngier
2020-02-14 14:57 ` [PATCH v4 10/20] irqchip/gic-v4.1: Move doorbell management to the GICv4 abstraction layer Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` [PATCH v4 11/20] irqchip/gic-v4.1: Add VSGI allocation/teardown Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` [PATCH v4 12/20] irqchip/gic-v4.1: Add VSGI property setup Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` [PATCH v4 13/20] irqchip/gic-v4.1: Eagerly vmap vPEs Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` [PATCH v4 14/20] KVM: arm64: GICv4.1: Let doorbells be auto-enabled Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` [PATCH v4 15/20] KVM: arm64: GICv4.1: Add direct injection capability to SGI registers Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-18 8:46 ` Zenghui Yu
2020-02-18 8:46 ` Zenghui Yu
2020-02-18 8:46 ` Zenghui Yu
2020-02-18 9:41 ` Marc Zyngier
2020-02-18 9:41 ` Marc Zyngier
2020-02-18 9:41 ` Marc Zyngier
2020-02-14 14:57 ` [PATCH v4 16/20] KVM: arm64: GICv4.1: Allow SGIs to switch between HW and SW interrupts Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-20 3:55 ` Zenghui Yu
2020-02-20 3:55 ` Zenghui Yu
2020-02-20 3:55 ` Zenghui Yu
2020-02-28 19:16 ` Marc Zyngier
2020-02-28 19:16 ` Marc Zyngier
2020-02-28 19:16 ` Marc Zyngier
2020-03-02 2:40 ` Zenghui Yu
2020-03-02 2:40 ` Zenghui Yu
2020-03-02 2:40 ` Zenghui Yu
2020-02-14 14:57 ` [PATCH v4 17/20] KVM: arm64: GICv4.1: Plumb SGI implementation selection in the distributor Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` [PATCH v4 18/20] KVM: arm64: GICv4.1: Reload VLPI configuration on distributor enable/disable Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` [PATCH v4 19/20] KVM: arm64: GICv4.1: Allow non-trapping WFI when using HW SGIs Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` [PATCH v4 20/20] KVM: arm64: GICv4.1: Expose HW-based SGIs in debugfs Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
2020-02-14 14:57 ` Marc Zyngier
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=8c538d2e-5ec8-0fd0-8999-e43a847df4c1@huawei.com \
--to=yuzenghui@huawei.com \
--cc=eric.auger@redhat.com \
--cc=james.morse@arm.com \
--cc=jason@lakedaemon.net \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=maz@kernel.org \
--cc=rrichter@marvell.com \
--cc=suzuki.poulose@arm.com \
--cc=tglx@linutronix.de \
/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.