All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Orzel, Michal" <michal.orzel@amd.com>
To: Julian Vetter <julian.vetter@vates.tech>,
	<xen-devel@lists.xenproject.org>
Cc: "Anthony PERARD" <anthony.perard@vates.tech>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Julien Grall" <julien@xen.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Juergen Gross" <jgross@suse.com>,
	"Andrii Sultanov" <andriy.sultanov@vates.tech>,
	"Guillaume Thouvenin" <guillaume.thouvenin@vates.tech>,
	"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
	"Bertrand Marquis" <bertrand.marquis@arm.com>,
	"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
	"Oleksii Moisieiev" <oleksii_moisieiev@epam.com>,
	"Timothy Pearson" <tpearson@raptorengineering.com>,
	"Alistair Francis" <alistair.francis@wdc.com>,
	"Connor Davis" <connojdavis@gmail.com>,
	"Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
	"Teddy Astie" <teddy.astie@vates.tech>
Subject: Re: [PATCH v3 1/6] xen/arm: report proper GIC version via XEN_DOMCTL_getdomaininfo
Date: Mon, 17 Aug 2026 14:19:15 +0200	[thread overview]
Message-ID: <e052ac27-1ea9-4f30-9e6b-3dc879708262@amd.com> (raw)
In-Reply-To: <1784211104.8631fc262581453bbf619ec5b2062170.19f6b44e2b5000edb5@vates.tech>



On 16-Jul-26 16:11, Julian Vetter wrote:
> When creating a domain on ARM, and passing XEN_DOMCTL_CONFIG_GIC_NATIVE
> for the gic_version field in the struct xen_arch_domainconfig,
> arch_sanitise_domain_config() resolves this to the approrpiate GIC_V2 or
> GIC_V3 version the domain actually has, based on the host's
> gic_hw_version(). That value is stored in the domain as
> d->arch.vgic.version, but can't be queried through any other domctl
> later. Toolstacks that create and build a domain in the same call
> already have this info from the createdomain reply and never need to ask
> again.
> 
> Toolstacks that create a domain and build it later from a separate
> process do need to ask again. But, the ARM implementation only fills in
> info->flags and info->gpaddr_bits. info->arch_config is left zeroed, so
> XEN_DOMCTL_getdomaininfo always reports gic_version as
> XEN_DOMCTL_CONFIG_GIC_NATIVE (0) regardless of what was actually
> configured earlier.
> 
> Signed-off-by: Julian Vetter <julian.vetter@vates.tech>
> Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Michal Orzel <michal.orzel@amd.com>

~Michal



  reply	other threads:[~2026-08-17 12:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-16 14:06 [PATCH v3 0/6] Fix ARM domcreate Julian Vetter
2026-07-16 14:11 ` [PATCH v3 1/6] xen/arm: report proper GIC version via XEN_DOMCTL_getdomaininfo Julian Vetter
2026-08-17 12:19   ` Orzel, Michal [this message]
     [not found] ` <20260716141138.88265-1-julian.vetter@vates.tech>
2026-07-16 14:11   ` [PATCH v3 2/6] ARM/sysctl: Expose the supported guest GIC modes in physinfo Julian Vetter
2026-08-11 13:38     ` Andrew Cooper
2026-08-17 12:39     ` Orzel, Michal
2026-08-17 13:08       ` Andrew Cooper
2026-08-17 14:36         ` Orzel, Michal
2026-07-16 14:11   ` [PATCH v3 3/6] tools/arm: choose GIC version explicitly instead of relying on GIC_NATIVE Julian Vetter
2026-08-11 13:43     ` Andrew Cooper
2026-07-16 14:11   ` [PATCH v3 4/6] xen/arm: remove XEN_DOMCTL_CONFIG_GIC_NATIVE from the ABI Julian Vetter
2026-08-11 13:54     ` Andrew Cooper
2026-07-16 14:11   ` [PATCH v3 5/6] xen/arm: report clock_frequency via sysctl physinfo, not createdomain Julian Vetter
2026-07-16 14:38     ` Jan Beulich
2026-07-16 14:11   ` [PATCH v3 6/6] xen: make config argument const Julian Vetter
2026-08-11 13:59     ` Andrew Cooper

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=e052ac27-1ea9-4f30-9e6b-3dc879708262@amd.com \
    --to=michal.orzel@amd.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=alistair.francis@wdc.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=andriy.sultanov@vates.tech \
    --cc=anthony.perard@vates.tech \
    --cc=bertrand.marquis@arm.com \
    --cc=connojdavis@gmail.com \
    --cc=guillaume.thouvenin@vates.tech \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=julian.vetter@vates.tech \
    --cc=julien@xen.org \
    --cc=marmarek@invisiblethingslab.com \
    --cc=oleksii.kurochko@gmail.com \
    --cc=oleksii_moisieiev@epam.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=teddy.astie@vates.tech \
    --cc=tpearson@raptorengineering.com \
    --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.