All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH kvm-unit-tests] arm/arm64: gicv3: support two redistributor regions
Date: Tue, 4 Sep 2018 09:02:13 +0200	[thread overview]
Message-ID: <20180904070213.rkl4fchslnfs52sy@kamzik.brq.redhat.com> (raw)
In-Reply-To: <CAFEAcA-eb=k1SVS2k4GenTEUsKuLYdx1DJ1SzTk-bHYaJcY-zg@mail.gmail.com>

On Tue, Sep 04, 2018 at 01:49:11AM +0100, Peter Maydell wrote:
> On 3 September 2018 at 17:45, Andrew Jones <drjones@redhat.com> wrote:
> > We need to support two redistributor regions in order to support
> > more than 123 vcpus. Also bump NR_CPUS to 512, since that's what
> > KVM currently supports.
> 
> Wouldn't it be neater to support the arbitrary number
> of redistributor regions that the h/w spec allows and
> the dt can describe, rather than just the specific case
> of 2 regions that QEMU happens to use ?
>

It would be nicer, and I suppose it would be pretty easy to do
as well. kvm-unit-tests/arm has always been a balance between being
over-engineered for its purposes and being too hacky. In this case,
I was probably too hacky. Although KVM only supports up to 512 VCPUS
right now and these two regions support up to 635, so it'll be a while
before a third region will be needed.

If I find time I'll send a v2, but in the meantime it'd be good to
get test results with this version to be sure I didn't miss anything
else.

Thanks,
drew

      reply	other threads:[~2018-09-04  7:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 16:45 [PATCH kvm-unit-tests] arm/arm64: gicv3: support two redistributor regions Andrew Jones
2018-09-04  0:49 ` Peter Maydell
2018-09-04  7:02   ` Andrew Jones [this message]

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=20180904070213.rkl4fchslnfs52sy@kamzik.brq.redhat.com \
    --to=drjones@redhat.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=marc.zyngier@arm.com \
    --cc=peter.maydell@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 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.