All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
Cc: Jing Zhang <jingzhangos@google.com>, KVM <kvm@vger.kernel.org>,
	KVMARM <kvmarm@lists.linux.dev>,
	ARMLinux <linux-arm-kernel@lists.infradead.org>,
	Oliver Upton <oupton@google.com>, Will Deacon <will@kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	James Morse <james.morse@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Fuad Tabba <tabba@google.com>, Reiji Watanabe <reijiw@google.com>,
	Raghavendra Rao Ananta <rananta@google.com>,
	Suraj Jitindar Singh <surajjs@amazon.com>
Subject: Re: [PATCH v9 5/5] KVM: arm64: Refactor writings for PMUVer/CSV2/CSV3
Date: Fri, 02 Jun 2023 09:15:46 +0100	[thread overview]
Message-ID: <877csmp9e5.wl-maz@kernel.org> (raw)
In-Reply-To: <cdbbd0d45079d58afcc92318114f04e2a43f0fd7.camel@gmail.com>

On Fri, 02 Jun 2023 02:03:30 +0100,
Suraj Jitindar Singh <sjitindarsingh@gmail.com> wrote:
> 
> Hi,
> 
> With the patch set you posted I get some kvm unit tests failures due to
> being unable to update register values from userspace. I propose the
> following patch as a solution:
> 
> [PATCH 1/2] KVM: arm64: Update id_reg limit value based on per vcpu
>  flags

While I really appreciate your help here, can you please try and reply
to the latest version of the series? You still commenting on v9 while
v10 has been out for a while, and there is now v11 on the list.

This will help making your comments and potential fixes relevant.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
Cc: Jing Zhang <jingzhangos@google.com>, KVM <kvm@vger.kernel.org>,
	KVMARM <kvmarm@lists.linux.dev>,
	ARMLinux <linux-arm-kernel@lists.infradead.org>,
	Oliver Upton <oupton@google.com>, Will Deacon <will@kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	James Morse <james.morse@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Fuad Tabba <tabba@google.com>, Reiji Watanabe <reijiw@google.com>,
	Raghavendra Rao Ananta <rananta@google.com>,
	Suraj Jitindar Singh <surajjs@amazon.com>
Subject: Re: [PATCH v9 5/5] KVM: arm64: Refactor writings for PMUVer/CSV2/CSV3
Date: Fri, 02 Jun 2023 09:15:46 +0100	[thread overview]
Message-ID: <877csmp9e5.wl-maz@kernel.org> (raw)
In-Reply-To: <cdbbd0d45079d58afcc92318114f04e2a43f0fd7.camel@gmail.com>

On Fri, 02 Jun 2023 02:03:30 +0100,
Suraj Jitindar Singh <sjitindarsingh@gmail.com> wrote:
> 
> Hi,
> 
> With the patch set you posted I get some kvm unit tests failures due to
> being unable to update register values from userspace. I propose the
> following patch as a solution:
> 
> [PATCH 1/2] KVM: arm64: Update id_reg limit value based on per vcpu
>  flags

While I really appreciate your help here, can you please try and reply
to the latest version of the series? You still commenting on v9 while
v10 has been out for a while, and there is now v11 on the list.

This will help making your comments and potential fixes relevant.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

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

  reply	other threads:[~2023-06-02  8:15 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17  6:10 [PATCH v9 0/5] Support writable CPU ID registers from userspace Jing Zhang
2023-05-17  6:10 ` Jing Zhang
2023-05-17  6:10 ` [PATCH v9 1/5] KVM: arm64: Save ID registers' sanitized value per guest Jing Zhang
2023-05-17  6:10   ` Jing Zhang
2023-05-18  7:17   ` Shameerali Kolothum Thodi
2023-05-18  7:17     ` Shameerali Kolothum Thodi
2023-05-18 19:48     ` Jing Zhang
2023-05-18 19:48       ` Jing Zhang
2023-05-19  8:08       ` Shameerali Kolothum Thodi
2023-05-19  8:08         ` Shameerali Kolothum Thodi
2023-05-19 17:44         ` Jing Zhang
2023-05-19 17:44           ` Jing Zhang
2023-05-19 22:16           ` Reiji Watanabe
2023-05-19 22:16             ` Reiji Watanabe
2023-05-22 17:27             ` Jing Zhang
2023-05-22 17:27               ` Jing Zhang
2023-05-17  6:10 ` [PATCH v9 2/5] KVM: arm64: Use per guest ID register for ID_AA64PFR0_EL1.[CSV2|CSV3] Jing Zhang
2023-05-17  6:10   ` Jing Zhang
2023-05-19 23:52   ` Reiji Watanabe
2023-05-19 23:52     ` Reiji Watanabe
2023-05-22 17:23     ` Jing Zhang
2023-05-22 17:23       ` Jing Zhang
2023-05-17  6:10 ` [PATCH v9 3/5] KVM: arm64: Use per guest ID register for ID_AA64DFR0_EL1.PMUVer Jing Zhang
2023-05-17  6:10   ` Jing Zhang
2023-05-17  6:10 ` [PATCH v9 4/5] KVM: arm64: Reuse fields of sys_reg_desc for idreg Jing Zhang
2023-05-17  6:10   ` Jing Zhang
2023-05-17  6:10 ` [PATCH v9 5/5] KVM: arm64: Refactor writings for PMUVer/CSV2/CSV3 Jing Zhang
2023-05-17  6:10   ` Jing Zhang
2023-06-02  1:03   ` Suraj Jitindar Singh
2023-06-02  1:03     ` Suraj Jitindar Singh
2023-06-02  8:15     ` Marc Zyngier [this message]
2023-06-02  8:15       ` 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=877csmp9e5.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=alexandru.elisei@arm.com \
    --cc=james.morse@arm.com \
    --cc=jingzhangos@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=oupton@google.com \
    --cc=pbonzini@redhat.com \
    --cc=rananta@google.com \
    --cc=reijiw@google.com \
    --cc=sjitindarsingh@gmail.com \
    --cc=surajjs@amazon.com \
    --cc=suzuki.poulose@arm.com \
    --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.