All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien@xen.org>
To: Dongjiu Geng <gengdongjiu1@gmail.com>,
	Bertrand Marquis <Bertrand.Marquis@arm.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v4] xen/arm: Allow QEMU platform to be built with GICv2
Date: Sun, 23 Jan 2022 14:42:45 +0400	[thread overview]
Message-ID: <f016c6cb-0e57-0a53-94a9-47f0a89b1d77@xen.org> (raw)
In-Reply-To: <CABSBigSba0ENZ-AvDN7bPGNqS5zQKceL901BxhjR8pkRntgnrw@mail.gmail.com>

Hello,

On 18/01/2022 12:58, Dongjiu Geng wrote:
> Bertrand Marquis <Bertrand.Marquis@arm.com> 于2022年1月18日周二 16:48写道:
>>
>> Hi Dongju,
>>
>>> On 18 Jan 2022, at 08:45, Dongjiu Geng <gengdongjiu1@gmail.com> wrote:
>>>
>>> Julien Grall <julien@xen.org> 于2022年1月17日周一 22:16写道:
>>>>
>>>> Hi,
>>>>
>>>> On 17/01/2022 10:40, Dongjiu Geng wrote:
>>>>> It turns out that QEMU has been supporting GICv2 virtualization since
>>>>> v3.1.0. So remove the dependencies on GICv3.
>>>>
>>>>
>>>> Technically, the current form of CONFIG_QEMU allows the same binary to
>>>> boot on QEMU with GICv2 or GICv3.
>>>>
>>>>> If we want to use GICv3,
>>>>> we can select the QEMU_LEGACY configuration.
>>>>
>>>> AFAIK, GICv3 is not a legacy feature... So it feels a bit odd to name it
>>>> like that (see more below).
>>>
>>> Legacy means QEMU platform only supports GICV3, now it can support
>>> both GICv2 and GICv3. The scope of support has been expanded
>>> Not mean GICv3 is a legacy feature.
>>
>> You might be misleading a bit here.
>> In the current configuration, Xen support GICv2, GICv3 and vgic.
>> The only thing not supported is actually the new VGIC but this is an unsupported feature not fully functional which shall be used with caution.
>>
>> What issue exactly do you have in Qemu configured for gicv2 when you use the default configuration ?
> 
> I want to use NEW_VGIC with GICv2, but QEMU only select GICV3,  when
> GICv3 is select, the NEW_VGIC can not be used.   I try the NEW_VGIC
> with GICv2, not found issue. so I want to remove this limitation.
> If  you think we should not support NEW_VGIC feature,  we can ignore
> this patch.  thanks!

I would love to get the NEW_VGIC supported. But I think this is 
orthogonal to whether we want to allow CONFIG_QEMU to select it.

If we fully support the new vGIC (i.e vGICv3 is implemented) then it 
would be possible to select it with CONFIG_QEMU as the restriction 
(!GICV3) would not be present.

So I view the change here as temporary. The proposed change will have an 
impact on the existing users (i.e. CONFIG_QEMU will not work out of the 
box anymore when QEMU is configured with GICv3). In addition to that, 
the end solution doesn't look simple. So I think this is not a patch I 
am willing to see temporarily.

One possibility would be to create a new CONFIG for allowing to select 
NEW_VGIC. That said, I don't much like it. So I would say if you want to 
select NEW_VGIC then you want to use defconfig (which should contain 
enough to boot on QEMU with DT).

Cheers,

-- 
Julien Grall


      parent reply	other threads:[~2022-01-23 10:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17  6:40 [PATCH v4] xen/arm: Allow QEMU platform to be built with GICv2 Dongjiu Geng
2022-01-17  9:00 ` Bertrand Marquis
2022-01-17 11:12   ` Dongjiu Geng
2022-01-17 11:38     ` Bertrand Marquis
2022-01-17 11:49       ` Dongjiu Geng
2022-01-17 14:15 ` Julien Grall
2022-01-18  8:32   ` Bertrand Marquis
2022-01-18  8:45   ` Dongjiu Geng
2022-01-18  8:48     ` Bertrand Marquis
2022-01-18  8:58       ` Dongjiu Geng
2022-01-18  9:17         ` Bertrand Marquis
2022-01-19 11:30           ` Dongjiu Geng
2022-01-23 10:31             ` Julien Grall
2022-01-23 10:42         ` Julien Grall [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=f016c6cb-0e57-0a53-94a9-47f0a89b1d77@xen.org \
    --to=julien@xen.org \
    --cc=Bertrand.Marquis@arm.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=gengdongjiu1@gmail.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.