From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
"Julien Grall" <julien@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 for-4.20? 5/6] radix-tree: introduce RADIX_TREE{,_INIT}()
Date: Mon, 3 Feb 2025 17:58:41 +0100 [thread overview]
Message-ID: <3facc3f9-fd75-49f9-aa8e-ecee3c67dc80@suse.com> (raw)
In-Reply-To: <528e3341-45ce-4e82-bdb5-ee3dc72a6925@citrix.com>
On 03.02.2025 17:48, Andrew Cooper wrote:
> On 03/02/2025 4:26 pm, Jan Beulich wrote:
>> ... now that static initialization is possible. Use RADIX_TREE() for
>> pci_segments and ivrs_maps.
>>
>> Requested-by: Andrew Cooper <andrew.cooper3@citrix.com>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> I'd not considered having RADIX_TREE() but it's nicer than my attempt.
>
> However,
>
>> --- a/xen/include/xen/radix-tree.h
>> +++ b/xen/include/xen/radix-tree.h
>> @@ -72,6 +72,9 @@ struct radix_tree_root {
>> *** radix-tree API starts here **
>> */
>>
>> +#define RADIX_TREE_INIT() {}
>
> ... this ought to be (struct radix_tree_root){} so it can't be used with
> other types, and radix_tree_init() wants to become:
>
> void radix_tree_init(struct radix_tree_root *root)
> {
> *root = RADIX_TREE_INIT();
> }
>
> instead of the raw memset(), so the connection is retained.
Can do; in fact I did consider both, but omitted them for simplicity.
> Assuming you're happy with these adjustments, Reviewed-by: Andrew Cooper
> <andrew.cooper3@citrix.com>
Thanks.
Jan
next prev parent reply other threads:[~2025-02-03 16:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 16:22 [PATCH for-4.20 0/6] AMD/IOMMU: assorted corrections Jan Beulich
2025-02-03 16:24 ` [PATCH v2 for-4.20? 1/6] AMD/IOMMU: drop stray MSI enabling Jan Beulich
2025-02-03 16:54 ` Roger Pau Monné
2025-02-03 16:24 ` [PATCH v2 for-4.20 2/6] x86/PCI: init segments earlier Jan Beulich
2025-02-03 16:25 ` [PATCH v2 for-4.20 3/6] radix-tree: purge node allocation override hooks Jan Beulich
2025-02-03 16:29 ` Jan Beulich
2025-02-03 16:36 ` Andrew Cooper
2025-02-03 16:25 ` [PATCH v2 for-4.21 4/6] radix-tree: drop "root" parameters from radix_tree_node_{alloc,free}() Jan Beulich
2025-02-03 16:40 ` Andrew Cooper
2025-02-03 16:26 ` [PATCH v2 for-4.20? 5/6] radix-tree: introduce RADIX_TREE{,_INIT}() Jan Beulich
2025-02-03 16:48 ` Andrew Cooper
2025-02-03 16:58 ` Jan Beulich [this message]
2025-02-04 8:36 ` Jan Beulich
2025-02-04 8:45 ` Jan Beulich
2025-02-04 11:19 ` Andrew Cooper
2025-02-03 16:27 ` [PATCH v2 for-4.20? 6/6] PCI: drop pci_segments_init() Jan Beulich
2025-02-03 17:04 ` Andrew Cooper
2025-02-04 7:17 ` Jan Beulich
2025-02-03 17:18 ` Roger Pau Monné
2025-02-04 7:45 ` Jan Beulich
2025-02-04 7:51 ` Jan Beulich
2025-02-04 8:56 ` Roger Pau Monné
2025-02-04 9:53 ` Jan Beulich
2025-02-03 16:38 ` [PATCH for-4.20 0/6] AMD/IOMMU: assorted corrections Oleksii Kurochko
2025-02-03 16:55 ` Andrew Cooper
2025-02-04 7:14 ` Jan Beulich
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=3facc3f9-fd75-49f9-aa8e-ecee3c67dc80@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.com \
--cc=roger.pau@citrix.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.