From: Blue Swirl <blauwirbel@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] provide opaque CPUState to files that are compiled once
Date: Fri, 2 Apr 2010 19:05:03 +0300 [thread overview]
Message-ID: <m2kf43fc5581004020905ye50f1213ve4d5b0ab4159a6d4@mail.gmail.com> (raw)
In-Reply-To: <4BB610A7.8010006@redhat.com>
On 4/2/10, Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 04/02/2010 05:22 PM, Anthony Liguori wrote:
>
>
> > hw/* should never access CPUState.
> >
> > Can you give examples of when qemu-kvm needs this?
> >
>
> Indirectly via header files. The problem is that GCC poisoning complains
> on prototypes too.
>
> qemu-kvm.h references CPUState and includes cpu.h, so with the latest
> changes all files that include qemu-kvm.h break, even if they don't require
> qemu-kvm.h. With this patch they instead get the opaque definition via
> hw/hw.h (which includes cpu-common.h), and qemu-kvm.h can avoid including
> cpu.h.
This is why I added #ifndef NEED_CPU_H to kvm.h.
> Another example is the new apic.h file created by Blue Swirl. It
> references CPUState. It includes apic_get_irq_delivered, so I placed
> apic_set_irq_delivered there too. But apic_set_irq_delivered is used by
> i8259.c which is compiled once.
But i8259.c is compiled per target, grep Makefile.target?
> There are other similar cases. Without something like this patch as a
> stopgap measure, you have to make everything compile again per-target which
> is a huge mess of conflicts.
This is wrong. There are lot of other ways to handle the need without
resorting to per-target build.
next prev parent reply other threads:[~2010-04-02 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 14:45 [Qemu-devel] [PATCH] provide opaque CPUState to files that are compiled once Paolo Bonzini
2010-04-02 15:22 ` Anthony Liguori
2010-04-02 15:43 ` Paolo Bonzini
2010-04-02 16:05 ` Blue Swirl [this message]
2010-04-02 16:06 ` Paolo Bonzini
2010-04-02 16:18 ` Blue Swirl
2010-04-02 16:24 ` Anthony Liguori
2010-04-02 16:43 ` Paolo Bonzini
2010-04-02 17:36 ` Anthony Liguori
2010-04-02 17:46 ` Paolo Bonzini
2010-04-02 17:49 ` Anthony Liguori
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=m2kf43fc5581004020905ye50f1213ve4d5b0ab4159a6d4@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).