qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Andrew Jones <drjones@redhat.com>,
	qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: peter.maydell@linaro.org, richard.henderson@linaro.org,
	ishii.shuuichir@fujitsu.com
Subject: Re: [PATCH 3/4] target/arm/cpu64: Replace kvm_supported with sve_vq_supported
Date: Fri, 20 Aug 2021 09:23:32 +0200	[thread overview]
Message-ID: <018e12b5-ac0b-3f13-fc10-9f90191db106@redhat.com> (raw)
In-Reply-To: <20210819193758.149660-4-drjones@redhat.com>

On 8/19/21 9:37 PM, Andrew Jones wrote:
> Now that we have an ARMCPU member sve_vq_supported we no longer
> need the local kvm_supported bitmap for KVM's supported vector
> lengths.
> 
> Signed-off-by: Andrew Jones <drjones@redhat.com>
> ---
>  target/arm/cpu64.c | 19 +++++++++++--------
>  1 file changed, 11 insertions(+), 8 deletions(-)

Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>



  reply	other threads:[~2021-08-20  7:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 19:37 [PATCH 0/4] target/arm/cpu: Introduce sve_vq_supported bitmap Andrew Jones
2021-08-19 19:37 ` [PATCH 1/4] " Andrew Jones
2021-08-19 22:53   ` Philippe Mathieu-Daudé
2021-08-19 19:37 ` [PATCH 2/4] target/arm/kvm64: Ensure sve vls map is completely clear Andrew Jones
2021-08-19 22:52   ` Philippe Mathieu-Daudé
2021-08-19 19:37 ` [PATCH 3/4] target/arm/cpu64: Replace kvm_supported with sve_vq_supported Andrew Jones
2021-08-20  7:23   ` Philippe Mathieu-Daudé [this message]
2021-08-19 19:37 ` [PATCH 4/4] target/arm/cpu64: Validate sve vector lengths are supported Andrew Jones
2021-08-23 15:52   ` Andrew Jones
2021-08-23 15:53 ` [PATCH 0/4] target/arm/cpu: Introduce sve_vq_supported bitmap Andrew Jones

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=018e12b5-ac0b-3f13-fc10-9f90191db106@redhat.com \
    --to=philmd@redhat.com \
    --cc=drjones@redhat.com \
    --cc=ishii.shuuichir@fujitsu.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 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).