From: "Arnd Bergmann" <arnd@arndb.de>
To: "Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Arnd Bergmann" <arnd@kernel.org>,
"Juergen Gross" <jgross@suse.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
x86@kernel.org, "Stefano Stabellini" <sstabellini@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>,
"Peter Zijlstra" <peterz@infradead.org>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [v2] x86: xen: add missing prototypes
Date: Wed, 24 May 2023 10:20:00 +0200 [thread overview]
Message-ID: <9dd597c5-1abc-4a25-a1cd-d7488d9d5b33@app.fastmail.com> (raw)
In-Reply-To: <2e5e627e-9f7e-ae63-05a3-d2b55e0703ba@oracle.com>
On Wed, May 24, 2023, at 01:09, Boris Ostrovsky wrote:
> On 5/23/23 4:37 PM, Arnd Bergmann wrote:
>> On Sat, May 20, 2023, at 00:24, Boris Ostrovsky wrote:
>>> On 5/19/23 5:28 AM, Arnd Bergmann wrote:
>>
>> Not sure if there is much point for the second one, since
>> it's only called from assembler, so the #else path is
>> never seen, but I can do that for consistency if you
>> like.
>>
>> I generally prefer to avoid the extra #if checks
>> when there is no strict need for an empty stub.
>
> Do we need the empty stubs? Neither of these should be referenced if
> !SMP (or more precisely if !CONFIG_XEN_PV_SMP)
We don't need the prototypes at all for building, they
are only there to avoid the missing-prototype warning!
I added the stubs in v3 because you asked for an #ifdef,
and having an #ifdef without an else clause seemed even
weirder: that would only add complexity for something that
is already unused while making it harder to maintain or
use if an actual user comes up.
I'll let someone else figure out what you actually want
here.
Arnd
prev parent reply other threads:[~2023-05-24 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 9:28 Arnd Bergmann
2023-05-19 22:24 ` Boris Ostrovsky
2023-05-23 20:37 ` Arnd Bergmann
2023-05-23 23:09 ` Boris Ostrovsky
2023-05-24 8:20 ` Arnd Bergmann [this message]
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=9dd597c5-1abc-4a25-a1cd-d7488d9d5b33@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=peterz@infradead.org \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®