linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Zenghui Yu <yuzenghui@huawei.com>,
	Eric Auger <eric.auger@redhat.com>,
	Jason Cooper <jason@lakedaemon.net>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH 0/2] GICv4.1 fixes for 5.7
Date: Tue, 14 Apr 2020 10:50:11 +0100	[thread overview]
Message-ID: <20200414095013.2821418-1-maz@kernel.org> (raw)

Here's a couple of GICv4.1 fixes for issues that have been found
during the 5.7 merge window.

The first one implements the "Dirty+Valid" feature, where the
hypervisor can wait for the GIC to have finish parsing the VPT before
entering the guest. The feature was optional in GICv4.0, but is now
mandatory in GICv4.1, so let's take advantage of it.

The second patch fixes an issue where the kernel shouts about the
effective affinity of VSGIs not being updated, which is the absolute
truth. Let's fix it.

I plan to send these fixes as part of a bigger pull request for -rc2.

Thanks,

	M.

Marc Zyngier (2):
  irqchip/gic-v4.1: Add support for VPENDBASER's Dirty+Valid signaling
  irqchip/gic-v4.1: Update effective affinity of virtual SGIs

 drivers/irqchip/irq-gic-v3-its.c   | 20 ++++++++++++++++++++
 drivers/irqchip/irq-gic-v3.c       | 11 +++++++----
 include/linux/irqchip/arm-gic-v3.h |  2 ++
 3 files changed, 29 insertions(+), 4 deletions(-)

-- 
2.25.1


             reply	other threads:[~2020-04-14  9:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14  9:50 Marc Zyngier [this message]
2020-04-14  9:50 ` [PATCH 1/2] irqchip/gic-v4.1: Add support for VPENDBASER's Dirty+Valid signaling Marc Zyngier
2020-04-16  3:35   ` Zenghui Yu
2020-04-14  9:50 ` [PATCH 2/2] irqchip/gic-v4.1: Update effective affinity of virtual SGIs Marc Zyngier
2020-04-16  3:36   ` Zenghui Yu

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=20200414095013.2821418-1-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=eric.auger@redhat.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).