From: "Alejandro Vallejo" <alejandro.vallejo@cloud.com>
To: "Orzel, Michal" <michal.orzel@amd.com>, <xen-devel@lists.xenproject.org>
Cc: "Anthony PERARD" <anthony.perard@vates.tech>,
"Juergen Gross" <jgross@suse.com>,
"Luca Fancellu" <luca.fancellu@arm.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Julien Grall" <julien@xen.org>,
"Bertrand Marquis" <bertrand.marquis@arm.com>
Subject: Re: [PATCH] tools/arm: Fix nr_spis handling v2
Date: Tue, 25 Mar 2025 14:10:46 +0000 [thread overview]
Message-ID: <D8PEOOSAHKDM.24T29QJBK3MUN@cloud.com> (raw)
In-Reply-To: <66815d0d-9330-468e-b601-cb8aa6be1c36@amd.com>
On Mon Mar 24, 2025 at 3:31 PM GMT, Michal Orzel wrote:
>
>
> On 24/03/2025 16:22, Alejandro Vallejo wrote:
> >
> >
> > On Mon Mar 24, 2025 at 1:08 PM GMT, Michal Orzel wrote:
> >>
> >>
> >> On 19/03/2025 15:01, Alejandro Vallejo wrote:
> >>>
> >>> Doesn't this regenerate the golang bindings?
> >> FYI, it does not. The bindings are already there for NrSpis and default value is
> >> does not result in a change (for verification I checked max_grant_frames that
> >> uses LIBXL_MAX_GRANT_DEFAULT).
> >>
> >> ~Michal
> >
> > Oh, good then. Though it does raise the (completely separate) question of how
> > correct those bindings might be if they ignore the IDL's default values... :/
> Why ignore. AFAICS libxl_domain_build_info_init is called there to grab default
> values.
>
> ~Michal
Oh, so the default populator is itself autogenerated C with a golang binding
rather than native golang. Fair enough. The more you learn.
Cheers,
Alejandro
next prev parent reply other threads:[~2025-03-25 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 9:00 [PATCH] tools/arm: Fix nr_spis handling v2 Michal Orzel
2025-03-18 9:22 ` Luca Fancellu
2025-03-19 14:01 ` Alejandro Vallejo
2025-03-19 14:05 ` Andrew Cooper
2025-03-19 14:37 ` Orzel, Michal
2025-03-19 16:22 ` Alejandro Vallejo
2025-03-24 13:08 ` Orzel, Michal
2025-03-24 15:22 ` Alejandro Vallejo
2025-03-24 15:31 ` Orzel, Michal
2025-03-25 14:10 ` Alejandro Vallejo [this message]
2025-03-20 16:46 ` Anthony PERARD
2025-03-24 8:54 ` Orzel, Michal
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=D8PEOOSAHKDM.24T29QJBK3MUN@cloud.com \
--to=alejandro.vallejo@cloud.com \
--cc=anthony.perard@vates.tech \
--cc=bertrand.marquis@arm.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=luca.fancellu@arm.com \
--cc=michal.orzel@amd.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.