From: Bjoern Walk <bwalk@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: Steffen Eiden <seiden@linux.ibm.com>,
Andreas Grapentin <gra@linux.ibm.com>,
Bjoern Walk <bwalk@linux.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org (open list:Overall KVM CPUs)
Subject: [RFC Patch 2/8] kvm: Add header dependency in system/kvm.h explicitly
Date: Mon, 9 Nov 2026 18:10:28 +0100 [thread overview]
Message-ID: <20261109171036.3806884-3-bwalk@linux.ibm.com> (raw)
In-Reply-To: <20261109171036.3806884-1-bwalk@linux.ibm.com>
The target-specific code in system/kvm.h requires definitions from
hw/core/cpu.h (technichally exec/vaddr.h for `vaddr` and qemu/queue.h
for QTAILQ_ENTRY).
Add the dependency explicitly to avoid headaches with unknown type names
later on.
Signed-off-by: Bjoern Walk <bwalk@linux.ibm.com>
---
include/system/kvm.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/system/kvm.h b/include/system/kvm.h
index 26d55cc6..5d7c0f98 100644
--- a/include/system/kvm.h
+++ b/include/system/kvm.h
@@ -222,6 +222,7 @@ void kvm_irqchip_change_notify(void);
#ifdef COMPILING_PER_TARGET
#include "cpu.h"
+#include "hw/core/cpu.h"
/**
* kvm_update_guest_debug(): ensure KVM debug structures updated
--
2.56.0
next parent reply other threads:[~2026-11-09 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261109171036.3806884-1-bwalk@linux.ibm.com>
2026-11-09 17:10 ` Bjoern Walk [this message]
2026-11-09 17:10 ` [RFC Patch 3/8] kvm: Prefer including "system/kvm.h" over <linux/kvm.h> Bjoern Walk
2026-11-09 17:10 ` [RFC Patch 6/8] linux-headers: Update to post-processed KVM headers Bjoern Walk
2026-11-09 17:10 ` [RFC Patch 7/8] kvm: Adjust system/kvm.h for updated KVM kernel headers Bjoern Walk
2026-11-09 17:10 ` [RFC Patch 8/8] kvm: Explicitly include ARM-specific KVM UAPI headers Bjoern Walk
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=20261109171036.3806884-3-bwalk@linux.ibm.com \
--to=bwalk@linux.ibm.com \
--cc=gra@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seiden@linux.ibm.com \
/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