From: "Jürgen Groß" <jgross@suse.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] x86/irqflags: Fix build failure
Date: Mon, 19 Jan 2026 15:22:57 +0100 [thread overview]
Message-ID: <80b9f7be-6783-4727-8a44-7922221e4026@suse.com> (raw)
In-Reply-To: <20260119141045.GEaW47ZZ5VuSJ10VYh@fat_crate.local>
[-- Attachment #1.1.1: Type: text/plain, Size: 1081 bytes --]
On 19.01.26 15:10, Borislav Petkov wrote:
> On Mon, Jan 19, 2026 at 02:58:45PM +0100, Jürgen Groß wrote:
>> Ah, yes. The build error happens due to the change of io.h: instead of
>> including paravirt.h only paravirt-base.h is included. Obviously several
>> sources did include io.h and irqflags.h, but no other header including
>> paravirt.h.
>
> So your io set needs the paravirt pile from tip/x86/paravirt. So you can
> include paravirt.h in there and no need for a "fix" patch.
>
Sigh.
paravirt.h is a big hammer.
Switching to paravirt-base.h is part of the goal to reduce include hell
with paravirt.
Why do you insist on keeping irqflags.h inconsistent by not defining
some prototypes if CONFIG_PARAVIRT is set, but not CONFIG_PARAVIRT_XXL.
Commit 22cc5ca5de52 was just missing the part of my patch. It was wrong.
Should have moved the "#include <asm/paravirt.h>" from the
CONFIG_PARAVIRT_XXL to the CONFIG_PARAVIRT umbrella, just like my
patch.
Or do you really think everyone including irqflags.h should include
io.h, too?
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2026-01-19 14:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 16:10 Juergen Gross
2026-01-15 17:45 ` Borislav Petkov
2026-01-15 18:29 ` Jürgen Groß
2026-01-19 11:36 ` Borislav Petkov
2026-01-19 11:52 ` Jürgen Groß
2026-01-19 13:28 ` Borislav Petkov
2026-01-19 13:52 ` Jürgen Groß
2026-01-19 13:58 ` Jürgen Groß
2026-01-19 14:10 ` Borislav Petkov
2026-01-19 14:22 ` Jürgen Groß [this message]
2026-01-19 15:46 ` Borislav Petkov
2026-01-19 16:02 ` Jürgen Groß
2026-01-19 16:24 ` Borislav Petkov
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=80b9f7be-6783-4727-8a44-7922221e4026@suse.com \
--to=jgross@suse.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.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®