From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"George Dunlap" <george.dunlap@citrix.com>,
"Ian Jackson" <iwj@xenproject.org>,
"Julien Grall" <julien@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>,
"Juergen Gross" <jgross@suse.com>
Subject: [PATCH 08/11] hypfs: avoid effectively open-coding xzalloc_array()
Date: Thu, 8 Apr 2021 14:21:13 +0200 [thread overview]
Message-ID: <eecf9929-30ee-424d-a371-1462c04cd382@suse.com> (raw)
In-Reply-To: <a3fef3b0-c9f3-208e-3728-62ca9cff70ba@suse.com>
There is a difference in generated code: xzalloc_bytes() forces
SMP_CACHE_BYTES alignment. I think we not only don't need this here, but
actually don't want it.
To avoid the need to add a cast, do away with the only forward-declared
struct hypfs_dyndata.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
--- a/xen/common/hypfs.c
+++ b/xen/common/hypfs.c
@@ -72,7 +72,7 @@ enum hypfs_lock_state {
hypfs_write_locked
};
static DEFINE_PER_CPU(enum hypfs_lock_state, hypfs_locked);
-static DEFINE_PER_CPU(struct hypfs_dyndata *, hypfs_dyndata);
+static DEFINE_PER_CPU(void *, hypfs_dyndata);
static DEFINE_PER_CPU(const struct hypfs_entry *, hypfs_last_node_entered);
@@ -160,19 +160,19 @@ static void node_exit_all(void)
void *hypfs_alloc_dyndata(unsigned long size)
{
unsigned int cpu = smp_processor_id();
- struct hypfs_dyndata **dyndata = &per_cpu(hypfs_dyndata, cpu);
+ void **dyndata = &per_cpu(hypfs_dyndata, cpu);
ASSERT(per_cpu(hypfs_locked, cpu) != hypfs_unlocked);
ASSERT(*dyndata == NULL);
- *dyndata = xzalloc_bytes(size);
+ *dyndata = xzalloc_array(unsigned char, size);
return *dyndata;
}
void *hypfs_get_dyndata(void)
{
- struct hypfs_dyndata *dyndata = this_cpu(hypfs_dyndata);
+ void *dyndata = this_cpu(hypfs_dyndata);
ASSERT(dyndata);
@@ -181,7 +181,7 @@ void *hypfs_get_dyndata(void)
void hypfs_free_dyndata(void)
{
- struct hypfs_dyndata **dyndata = &this_cpu(hypfs_dyndata);
+ void **dyndata = &this_cpu(hypfs_dyndata);
XFREE(*dyndata);
}
next prev parent reply other threads:[~2021-04-08 12:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 12:13 [PATCH 00/11] assorted replacement of x[mz]alloc_bytes() Jan Beulich
2021-04-08 12:16 ` [PATCH 01/11] x86/HVM: avoid effectively open-coding xzalloc_flex_struct() Jan Beulich
2021-04-08 12:20 ` Andrew Cooper
2021-04-08 12:17 ` [PATCH 02/11] x86/vPMU: " Jan Beulich
2021-04-08 12:25 ` Andrew Cooper
2021-04-08 12:29 ` Jan Beulich
2021-04-08 12:17 ` [PATCH 03/11] x86/MCE: avoid effectively open-coding xmalloc_array() Jan Beulich
2021-04-08 12:18 ` [PATCH 04/11] x86/HVM: " Jan Beulich
2021-04-08 12:19 ` [PATCH 05/11] x86/oprofile: " Jan Beulich
2021-04-08 12:20 ` [PATCH 06/11] x86/IRQ: avoid over-alignment in alloc_pirq_struct() Jan Beulich
2021-04-08 12:20 ` [PATCH 07/11] EFI/runtime: avoid effectively open-coding xmalloc_array() Jan Beulich
2021-04-08 12:21 ` Jan Beulich [this message]
2021-04-08 14:28 ` [PATCH 08/11] hypfs: avoid effectively open-coding xzalloc_array() Juergen Gross
2021-04-08 12:21 ` [PATCH 09/11] kexec: avoid effectively open-coding xzalloc_flex_struct() Jan Beulich
2021-04-09 12:54 ` Andrew Cooper
2021-04-09 13:23 ` Jan Beulich
2021-04-08 12:22 ` [PATCH 10/11] video/lfb: avoid effectively open-coding xzalloc_array() Jan Beulich
2021-04-08 12:23 ` [PATCH 11/11] Arm/optee: don't open-code xzalloc_flex_struct() Jan Beulich
2021-04-13 18:19 ` Julien Grall
2021-04-14 7:03 ` Jan Beulich
2021-04-15 10:26 ` Julien Grall
2021-04-15 11:02 ` Jan Beulich
2021-04-15 11:31 ` Julien Grall
2021-04-08 12:57 ` [PATCH 00/11] assorted replacement of x[mz]alloc_bytes() Andrew Cooper
2021-04-08 14:12 ` 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=eecf9929-30ee-424d-a371-1462c04cd382@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=roger.pau@citrix.com \
--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).