From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Igor Druzhinin <igor.druzhinin@citrix.com>,
Jan Beulich <jbeulich@suse.com>
Cc: <iwj@xenproject.org>, <wl@xen.org>, <george.dunlap@citrix.com>,
<julien@xen.org>, <sstabellini@kernel.org>, <jgross@suse.com>,
<christian.lindig@citrix.com>, <dave@recoil.org>,
<xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] tools/libxc: use uint32_t for pirq in xc_domain_irq_permission
Date: Thu, 8 Jul 2021 02:11:09 +0100 [thread overview]
Message-ID: <ea392b06-6277-ced8-0cbc-40967fc1ca61@citrix.com> (raw)
In-Reply-To: <5dfb0321-ca52-5464-8bbb-c29d329d24cf@citrix.com>
On 08/07/2021 02:08, Igor Druzhinin wrote:
> On 07/07/2021 10:19, Andrew Cooper wrote:
>> On 07/07/2021 08:46, Jan Beulich wrote:
>>>> --- a/tools/include/xenctrl.h
>>>> +++ b/tools/include/xenctrl.h
>>>> @@ -1385,7 +1385,7 @@ int xc_domain_ioport_permission(xc_interface
>>>> *xch,
>>>> int xc_domain_irq_permission(xc_interface *xch,
>>>> uint32_t domid,
>>>> - uint8_t pirq,
>>>> + uint32_t pirq,
>>>> uint8_t allow_access);
>>> Take the opportunity and also change "allow_access" to bool? Or is
>>> use of bool prohibited in external interfaces?
>>
>> We've got bool's in the interface already.
>
> Where exactly? I couldn't find a single "bool".
$ git grep -w bool -- :/tools/include/xen*.h
../tools/include/xenctrl.h:1844: uint32_t
domid, bool restore,
../tools/include/xenctrl.h:1846: unsigned int
nr_features, bool pae, bool itsc,
../tools/include/xenctrl.h:1847: bool
nested_virt, const struct xc_xend_cpuid *xend);
../tools/include/xenctrl.h:1954:int
xc_altp2m_get_domain_state(xc_interface *handle, uint32_t dom, bool *state);
../tools/include/xenctrl.h:1955:int
xc_altp2m_set_domain_state(xc_interface *handle, uint32_t dom, bool state);
and loads more.
~Andrew
next prev parent reply other threads:[~2021-07-08 1:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 1:02 [PATCH] tools/libxc: use uint32_t for pirq in xc_domain_irq_permission Igor Druzhinin
2021-07-07 7:46 ` Jan Beulich
2021-07-07 9:19 ` Andrew Cooper
2021-07-08 1:08 ` Igor Druzhinin
2021-07-08 1:11 ` Andrew Cooper [this message]
2021-07-08 1:14 ` Igor Druzhinin
2021-07-08 1:26 ` Andrew Cooper
2021-07-08 1:30 ` Igor Druzhinin
2021-07-07 8:48 ` Christian Lindig
2021-07-07 12:51 ` Julien Grall
2021-07-07 12:54 ` Jan Beulich
2021-07-07 12:59 ` Julien Grall
2021-07-07 13:14 ` Jan Beulich
2021-07-07 13:21 ` Julien Grall
2021-07-07 13:25 ` Jan Beulich
2021-07-08 2:06 ` Igor Druzhinin
2021-07-12 8:59 ` Julien Grall
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=ea392b06-6277-ced8-0cbc-40967fc1ca61@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=christian.lindig@citrix.com \
--cc=dave@recoil.org \
--cc=george.dunlap@citrix.com \
--cc=igor.druzhinin@citrix.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).