All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org,
	kernel-team@android.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v4 2/6] hw/arm/virt: Add a control for the the highmem redistributors
Date: Mon, 10 Jan 2022 16:02:04 +0000	[thread overview]
Message-ID: <87h7abtw8z.wl-maz@kernel.org> (raw)
In-Reply-To: <CAFEAcA-OF29ptHr0X9ojyLEcDw9v7Smc5PC3O+v5Uv3bjiSmRA@mail.gmail.com>

On Mon, 10 Jan 2022 15:47:47 +0000,
Peter Maydell <peter.maydell@linaro.org> wrote:
> 
> On Mon, 10 Jan 2022 at 15:45, Marc Zyngier <maz@kernel.org> wrote:
> > $ /home/maz/vminstall/qemu-hack -m 1G -smp 256 -cpu host -machine virt,accel=kvm,gic-version=3,highmem=on -nographic -drive if=pflash,format=raw,readonly=on,file=/usr/share/AAVMF/AAVMF_CODE.fd
> > qemu-hack: warning: Number of SMP cpus requested (256) exceeds the recommended cpus supported by KVM (8)
> > qemu-hack: warning: Number of hotpluggable cpus requested (256) exceeds the recommended cpus supported by KVM (8)
> > qemu-hack: Capacity of the redist regions(123) is less than number of vcpus(256)
> 
> Side question: why is KVM_CAP_NR_VCPUS returning 8 for
> "recommended cpus supported by KVM" ? Is something still
> assuming GICv2 CPU limits?

No, it is only that KVM_CAP_NR_VCPUS is defined as returning the
number of physical CPUs (and this test machine has only 8 of them).

	M.

-- 
Without deviation from the norm, progress is not possible.
_______________________________________________
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: Peter Maydell <peter.maydell@linaro.org>
Cc: eric.auger@redhat.com, qemu-devel@nongnu.org,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
	kernel-team@android.com, Andrew Jones <drjones@redhat.com>
Subject: Re: [PATCH v4 2/6] hw/arm/virt: Add a control for the the highmem redistributors
Date: Mon, 10 Jan 2022 16:02:04 +0000	[thread overview]
Message-ID: <87h7abtw8z.wl-maz@kernel.org> (raw)
In-Reply-To: <CAFEAcA-OF29ptHr0X9ojyLEcDw9v7Smc5PC3O+v5Uv3bjiSmRA@mail.gmail.com>

On Mon, 10 Jan 2022 15:47:47 +0000,
Peter Maydell <peter.maydell@linaro.org> wrote:
> 
> On Mon, 10 Jan 2022 at 15:45, Marc Zyngier <maz@kernel.org> wrote:
> > $ /home/maz/vminstall/qemu-hack -m 1G -smp 256 -cpu host -machine virt,accel=kvm,gic-version=3,highmem=on -nographic -drive if=pflash,format=raw,readonly=on,file=/usr/share/AAVMF/AAVMF_CODE.fd
> > qemu-hack: warning: Number of SMP cpus requested (256) exceeds the recommended cpus supported by KVM (8)
> > qemu-hack: warning: Number of hotpluggable cpus requested (256) exceeds the recommended cpus supported by KVM (8)
> > qemu-hack: Capacity of the redist regions(123) is less than number of vcpus(256)
> 
> Side question: why is KVM_CAP_NR_VCPUS returning 8 for
> "recommended cpus supported by KVM" ? Is something still
> assuming GICv2 CPU limits?

No, it is only that KVM_CAP_NR_VCPUS is defined as returning the
number of physical CPUs (and this test machine has only 8 of them).

	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: Peter Maydell <peter.maydell@linaro.org>
Cc: Andrew Jones <drjones@redhat.com>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org,
	eric.auger@redhat.com, kernel-team@android.com,
	kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v4 2/6] hw/arm/virt: Add a control for the the highmem redistributors
Date: Mon, 10 Jan 2022 16:02:04 +0000	[thread overview]
Message-ID: <87h7abtw8z.wl-maz@kernel.org> (raw)
In-Reply-To: <CAFEAcA-OF29ptHr0X9ojyLEcDw9v7Smc5PC3O+v5Uv3bjiSmRA@mail.gmail.com>

On Mon, 10 Jan 2022 15:47:47 +0000,
Peter Maydell <peter.maydell@linaro.org> wrote:
> 
> On Mon, 10 Jan 2022 at 15:45, Marc Zyngier <maz@kernel.org> wrote:
> > $ /home/maz/vminstall/qemu-hack -m 1G -smp 256 -cpu host -machine virt,accel=kvm,gic-version=3,highmem=on -nographic -drive if=pflash,format=raw,readonly=on,file=/usr/share/AAVMF/AAVMF_CODE.fd
> > qemu-hack: warning: Number of SMP cpus requested (256) exceeds the recommended cpus supported by KVM (8)
> > qemu-hack: warning: Number of hotpluggable cpus requested (256) exceeds the recommended cpus supported by KVM (8)
> > qemu-hack: Capacity of the redist regions(123) is less than number of vcpus(256)
> 
> Side question: why is KVM_CAP_NR_VCPUS returning 8 for
> "recommended cpus supported by KVM" ? Is something still
> assuming GICv2 CPU limits?

No, it is only that KVM_CAP_NR_VCPUS is defined as returning the
number of physical CPUs (and this test machine has only 8 of them).

	M.

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


  reply	other threads:[~2022-01-10 16:02 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 16:33 [PATCH v4 0/6] target/arm: Reduced-IPA space and highmem fixes Marc Zyngier
2022-01-07 16:33 ` Marc Zyngier
2022-01-07 16:33 ` Marc Zyngier
2022-01-07 16:33 ` [PATCH v4 1/6] hw/arm/virt: Add a control for the the highmem PCIe MMIO Marc Zyngier
2022-01-07 16:33   ` Marc Zyngier
2022-01-07 16:33   ` Marc Zyngier
2022-01-07 16:33 ` [PATCH v4 2/6] hw/arm/virt: Add a control for the the highmem redistributors Marc Zyngier
2022-01-07 16:33   ` Marc Zyngier
2022-01-07 16:33   ` Marc Zyngier
2022-01-10 15:35   ` Eric Auger
2022-01-10 15:35     ` Eric Auger
2022-01-10 15:35     ` Eric Auger
2022-01-10 15:45     ` Marc Zyngier
2022-01-10 15:45       ` Marc Zyngier
2022-01-10 15:45       ` Marc Zyngier
2022-01-10 15:47       ` Peter Maydell
2022-01-10 15:47         ` Peter Maydell
2022-01-10 15:47         ` Peter Maydell
2022-01-10 16:02         ` Marc Zyngier [this message]
2022-01-10 16:02           ` Marc Zyngier
2022-01-10 16:02           ` Marc Zyngier
2022-01-10 15:48       ` Eric Auger
2022-01-10 15:48         ` Eric Auger
2022-01-10 15:48         ` Eric Auger
2022-01-07 16:33 ` [PATCH v4 3/6] hw/arm/virt: Honor highmem setting when computing the memory map Marc Zyngier
2022-01-07 16:33   ` Marc Zyngier
2022-01-07 16:33   ` Marc Zyngier
2022-01-10 15:30   ` Eric Auger
2022-01-10 15:30     ` Eric Auger
2022-01-10 15:30     ` Eric Auger
2022-01-07 16:33 ` [PATCH v4 4/6] hw/arm/virt: Use the PA range to compute " Marc Zyngier
2022-01-07 16:33   ` Marc Zyngier
2022-01-07 16:33   ` Marc Zyngier
2022-01-10 15:38   ` Eric Auger
2022-01-10 15:38     ` Eric Auger
2022-01-10 15:38     ` Eric Auger
2022-01-10 15:58     ` Marc Zyngier
2022-01-10 15:58       ` Marc Zyngier
2022-01-10 15:58       ` Marc Zyngier
2022-01-07 16:33 ` [PATCH v4 5/6] hw/arm/virt: Disable highmem devices that don't fit in the PA range Marc Zyngier
2022-01-07 16:33   ` Marc Zyngier
2022-01-07 16:33   ` Marc Zyngier
2022-01-10 17:12   ` Eric Auger
2022-01-10 17:12     ` Eric Auger
2022-01-10 17:12     ` Eric Auger
2022-01-10 18:51     ` Marc Zyngier
2022-01-10 18:51       ` Marc Zyngier
2022-01-10 18:51       ` Marc Zyngier
2022-01-07 16:33 ` [PATCH v4 6/6] hw/arm/virt: Drop superfluous checks against highmem Marc Zyngier
2022-01-07 16:33   ` Marc Zyngier
2022-01-07 16:33   ` Marc Zyngier
2022-01-10 17:14   ` Eric Auger
2022-01-10 17:14     ` Eric Auger
2022-01-10 17:14     ` Eric Auger

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=87h7abtw8z.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=kernel-team@android.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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.