All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Fuad Tabba <tabba@google.com>
Cc: kernel-team@android.com, catalin.marinas@arm.com,
	will@kernel.org, kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/4] KVM: arm64: Do not communicate host pmu event changes by accessing hyp data
Date: Sun, 15 May 2022 11:29:02 +0100	[thread overview]
Message-ID: <0b9180b7b093e4fb6d7394041b526c96@kernel.org> (raw)
In-Reply-To: <20220510095710.148178-1-tabba@google.com>

Hi Fuad,

On 2022-05-10 10:57, Fuad Tabba wrote:
> Hi,
> 
> This series changes the way KVM communicates host pmu event changes to 
> the
> hypervisor in nvhe and protected mode. Instead of accessing hyp data 
> directly
> from the host, the data is passed to hyp via the loaded vcpu. This 
> provides
> more isolation between the host and the hypervisor, and allows us to 
> use pmu in
> protected mode.
> 
> This series is based on kvmarm/next (8c22fd2d4cfa).

In the future, please don't do that. *Always* base your patches
on something stable (preferably an early -rc, as I usually start
pulling stuff in around -rc3).

kvmarm/next is a moving target, and basing things on top of it
results in an uncontrolled dependency chain. If your series depends
on something and makes it impossible to base your patches on an rc,
please state so (this isn't the case here).

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...
_______________________________________________
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: Marc Zyngier <maz@kernel.org>
To: Fuad Tabba <tabba@google.com>
Cc: kvmarm@lists.cs.columbia.edu, will@kernel.org,
	qperret@google.com, james.morse@arm.com,
	alexandru.elisei@arm.com, suzuki.poulose@arm.com,
	catalin.marinas@arm.com, drjones@redhat.com, oupton@google.com,
	linux-arm-kernel@lists.infradead.org, kernel-team@android.com
Subject: Re: [PATCH v4 0/4] KVM: arm64: Do not communicate host pmu event changes by accessing hyp data
Date: Sun, 15 May 2022 11:29:02 +0100	[thread overview]
Message-ID: <0b9180b7b093e4fb6d7394041b526c96@kernel.org> (raw)
In-Reply-To: <20220510095710.148178-1-tabba@google.com>

Hi Fuad,

On 2022-05-10 10:57, Fuad Tabba wrote:
> Hi,
> 
> This series changes the way KVM communicates host pmu event changes to 
> the
> hypervisor in nvhe and protected mode. Instead of accessing hyp data 
> directly
> from the host, the data is passed to hyp via the loaded vcpu. This 
> provides
> more isolation between the host and the hypervisor, and allows us to 
> use pmu in
> protected mode.
> 
> This series is based on kvmarm/next (8c22fd2d4cfa).

In the future, please don't do that. *Always* base your patches
on something stable (preferably an early -rc, as I usually start
pulling stuff in around -rc3).

kvmarm/next is a moving target, and basing things on top of it
results in an uncontrolled dependency chain. If your series depends
on something and makes it impossible to base your patches on an rc,
please state so (this isn't the case here).

Thanks,

         M.
-- 
Jazz is not dead. It just smells funny...

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-05-15 10:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10  9:57 [PATCH v4 0/4] KVM: arm64: Do not communicate host pmu event changes by accessing hyp data Fuad Tabba
2022-05-10  9:57 ` Fuad Tabba
2022-05-10  9:57 ` [PATCH v4 1/4] KVM: arm64: Wrapper for getting pmu_events Fuad Tabba
2022-05-10  9:57   ` Fuad Tabba
2022-05-10  9:57 ` [PATCH v4 2/4] KVM: arm64: Repack struct kvm_pmu to reduce size Fuad Tabba
2022-05-10  9:57   ` Fuad Tabba
2022-05-10  9:57 ` [PATCH v4 3/4] KVM: arm64: Pass pmu events to hyp via vcpu Fuad Tabba
2022-05-10  9:57   ` Fuad Tabba
2022-05-10 18:07   ` Oliver Upton
2022-05-10 18:07     ` Oliver Upton
2022-05-10  9:57 ` [PATCH v4 4/4] KVM: arm64: Reenable pmu in Protected Mode Fuad Tabba
2022-05-10  9:57   ` Fuad Tabba
2022-05-10 18:07   ` Oliver Upton
2022-05-10 18:07     ` Oliver Upton
2022-05-15 10:29 ` Marc Zyngier [this message]
2022-05-15 10:29   ` [PATCH v4 0/4] KVM: arm64: Do not communicate host pmu event changes by accessing hyp data Marc Zyngier
2022-05-15 10:57 ` Marc Zyngier
2022-05-15 10: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=0b9180b7b093e4fb6d7394041b526c96@kernel.org \
    --to=maz@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=tabba@google.com \
    --cc=will@kernel.org \
    /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.