All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Auger <eric.auger@linaro.org>
To: Pavel Fedin <p.fedin@samsung.com>,
	'Ashok Kumar' <ashoks@broadcom.com>,
	qemu-devel@nongnu.org
Cc: 'Shlomo Pongratz' <shlomo.pongratz@huawei.com>
Subject: Re: [Qemu-devel] [RFC PATCH] hw/arm/virt: Added preliminary GICv3 support for kvm mode
Date: Thu, 21 May 2015 16:24:27 +0200	[thread overview]
Message-ID: <555DEA9B.7070306@linaro.org> (raw)
In-Reply-To: <014801d093cf$da300d80$8e902880$@samsung.com>

On 05/21/2015 04:10 PM, Pavel Fedin wrote:
>  Hello!
> 
>> So to me it is sensible to instantiate GICV2 through legacy
>> KVM_CREATE_IRQCHIP API if both KVM_CREATE_DEVICE(test mode=true) failed.
> 
>  I disagree because at this point we already know which GIC version the user wants. This
> is because kvm_irqchip_create() is called after machine instance is created (and
> virt_instance_init() has been called). At this point we already know all the options. At
> this point i think the scenario should be:
>  a) If we want GICv3 - test for KVM_CREATE_DEVICE(GICv3) and fail if we don't have one.
>  b) If we want GICv2 - test for KVM_CREATE_DEVICE(GICv2). If it fails, try
> KVM_CREATE_IRQCHIP.
>  IMHO there is little sense to fall back from v3 to v2 or vice versa because other
> important parameters (like number of CPUs) depend on it.
>  Implementing this behavior costs only one more integer in MachineState structure. Is it
> too large ? If you want, i can post my patches as RFC, i think now they are more or less
> OK.

Hi Pavel,

yes sure please post your RFC and let's wait for other reviewer
feedback. I just shared my understanding ;-)

Best Regards

Eric
> 
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
> 
> 

  reply	other threads:[~2015-05-21 14:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 17:27 [Qemu-devel] [RFC PATCH] hw/arm/virt: Added preliminary GICv3 support for kvm mode Ashok Kumar
2015-05-15  6:42 ` Pavel Fedin
2015-05-19 12:50   ` Eric Auger
2015-05-21  6:47     ` Pavel Fedin
2015-05-21  8:59       ` Eric Auger
2015-05-21 14:10         ` Pavel Fedin
2015-05-21 14:24           ` Eric Auger [this message]
2015-05-19 16:45   ` Eric Auger
2015-05-18 15:44 ` Eric Auger
2015-05-19 12:52   ` Eric Auger
  -- strict thread matches above, loose matches on Subject: below --
2015-05-14 20:13 Ashok Kumar

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=555DEA9B.7070306@linaro.org \
    --to=eric.auger@linaro.org \
    --cc=ashoks@broadcom.com \
    --cc=p.fedin@samsung.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shlomo.pongratz@huawei.com \
    /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.