All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>
Cc: kvmarm@lists.linux.dev, Joey Gouly <joey.gouly@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH 2/2] KVM: arm64: Ensure vgic_ready() is ordered against MMIO registration
Date: Thu, 17 Oct 2024 08:53:30 -0700	[thread overview]
Message-ID: <ZxEy-swdecozHK7z@linux.dev> (raw)
In-Reply-To: <86ttdb40ux.wl-maz@kernel.org>

On Thu, Oct 17, 2024 at 08:58:30AM +0100, Marc Zyngier wrote:
> On Thu, 17 Oct 2024 01:19:47 +0100, Oliver Upton <oliver.upton@linux.dev> wrote:
> I thought we would benefit from the removal of the early-out at the
> beginning of the function, specially given that this is only called on
> the first run of any vcpu -- and we can probably afford to take the
> locks on such a rare event. My impression is that we'd gain in
> robustness and maintainability.
> 
> This can come as a later patch if we agree that this is valuable.

I should've mentioned my rationale a bit more here, thanks for queuing
the patch anyway. Prolonged blackout for live migration is a problem for
larger VMs, and I was too chicken to have all vCPUs pile up on slots_lock
and config_lock.

Too lazy to prove this is/isn't an issue, so I figured I'd preserve the
existing flow as much as possible. If we get this wrong again (which
wouldn't be surprising) then let's drop the early out and just take the
locks.

Seem reasonable?

-- 
Thanks,
Oliver

  reply	other threads:[~2024-10-17 15:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  0:19 [PATCH 0/2] KVM: arm64: Ensure VGIC is fully initialized before entering guest Oliver Upton
2024-10-17  0:19 ` [PATCH 1/2] KVM: arm64: vgic: Don't check for vgic_ready() when setting NR_IRQS Oliver Upton
2024-10-17  0:19 ` [PATCH 2/2] KVM: arm64: Ensure vgic_ready() is ordered against MMIO registration Oliver Upton
2024-10-17  7:58   ` Marc Zyngier
2024-10-17 15:53     ` Oliver Upton [this message]
2024-10-17  0:22 ` [PATCH 0/2] KVM: arm64: Ensure VGIC is fully initialized before entering guest Oliver Upton
2024-10-17  8:23 ` 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=ZxEy-swdecozHK7z@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=joey.gouly@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=maz@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --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 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.