From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, alex.bennee@linaro.org,
Marcelo Tosatti <mtosatti@redhat.com>,
"Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>,
richard.henderson@linaro.org, manos.pitsidianakis@linaro.org
Subject: Re: [PATCH v4 2/7] hw/hyperv/hyperv.h: header cleanup
Date: Tue, 11 Mar 2025 16:14:36 +0100 [thread overview]
Message-ID: <b5f9e231-8c29-4992-89a0-5cdea7c08b34@linaro.org> (raw)
In-Reply-To: <f957fbdb-c7c3-4a31-a76a-144ff31ea158@linaro.org>
On 11/3/25 16:05, Philippe Mathieu-Daudé wrote:
> On 7/3/25 22:56, Pierrick Bouvier wrote:
>> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
>> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
>> ---
>> include/hw/hyperv/hyperv.h | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/hw/hyperv/hyperv.h b/include/hw/hyperv/hyperv.h
>> index d717b4e13d4..63a8b65278f 100644
>> --- a/include/hw/hyperv/hyperv.h
>> +++ b/include/hw/hyperv/hyperv.h
>> @@ -10,7 +10,8 @@
>> #ifndef HW_HYPERV_HYPERV_H
>> #define HW_HYPERV_HYPERV_H
>> -#include "cpu-qom.h"
>> +#include "exec/hwaddr.h"
>> +#include "hw/core/cpu.h"
>
> I don't see where "hw/core/cpu.h" is used.
OK found it:
static inline uint32_t hyperv_vp_index(CPUState *cs)
{
return cs->cpu_index;
}
First, bringing this huge header for this single use is way overkill,
then I doubt this method deserves to be inlined, third @cpu_index is
an accelerator specific field, often incorrectly used. Maybe in this
case it is OK although, since IIUC we only support HyperV with KVM,
right?
next prev parent reply other threads:[~2025-03-11 15:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 21:56 [PATCH v4 0/7] hw/hyperv: remove duplication compilation units Pierrick Bouvier
2025-03-07 21:56 ` [PATCH v4 1/7] hw/hyperv/hv-balloon-stub: common compilation unit Pierrick Bouvier
2025-03-07 21:56 ` [PATCH v4 2/7] hw/hyperv/hyperv.h: header cleanup Pierrick Bouvier
2025-03-11 15:05 ` Philippe Mathieu-Daudé
2025-03-11 15:14 ` Philippe Mathieu-Daudé [this message]
2025-03-07 21:56 ` [PATCH v4 3/7] hw/hyperv/vmbus: common compilation unit Pierrick Bouvier
2025-03-07 21:56 ` [PATCH v4 4/7] hw/hyperv/hyperv-proto: move SYNDBG definition from target/i386 Pierrick Bouvier
2025-03-07 21:56 ` [PATCH v4 5/7] hw/hyperv/syndbg: common compilation unit Pierrick Bouvier
2025-03-07 21:56 ` [PATCH v4 6/7] hw/hyperv/balloon: common balloon compilation units Pierrick Bouvier
2025-03-07 21:56 ` [PATCH v4 7/7] hw/hyperv/hyperv_testdev: common compilation unit Pierrick Bouvier
2025-03-07 22:06 ` [PATCH v4 0/7] hw/hyperv: remove duplication compilation units Philippe Mathieu-Daudé
2025-03-07 22:38 ` Pierrick Bouvier
2025-03-07 22:25 ` Philippe Mathieu-Daudé
2025-03-07 22:31 ` Maciej S. Szmigiero
2025-03-07 22:37 ` Philippe Mathieu-Daudé
2025-03-09 23:33 ` Pierrick Bouvier
2025-03-10 0:14 ` Philippe Mathieu-Daudé
2025-03-10 2:10 ` Pierrick Bouvier
2025-03-10 12:28 ` Maciej S. Szmigiero
2025-03-10 12:28 ` Maciej S. Szmigiero
2025-03-20 19:00 ` Pierrick Bouvier
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=b5f9e231-8c29-4992-89a0-5cdea7c08b34@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=maciej.szmigiero@oracle.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).