From: Paolo Bonzini <pbonzini@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH 6/6] apic: avoid using CPUState internals
Date: Sun, 06 Jun 2010 19:39:45 +0200 [thread overview]
Message-ID: <4C0BDD61.9020908@redhat.com> (raw)
In-Reply-To: <AANLkTikMjEneitQJy0ABsx_sSYxCC3R2K95hXZ-J37zs@mail.gmail.com>
On 06/05/2010 11:31 PM, Blue Swirl wrote:
> Use only an opaque CPUState pointer and move the actual CPUState
> contents handling to cpu.h and cpuid.c.
>
> Set env->halted in pc.c and add a function to get the local APIC state
> of the current CPU for the MMIO.
>
> Signed-off-by: Blue Swirl<blauwirbel@gmail.com>
> ---
> hw/apic.c | 40 +++++++++++++++-------------------------
> hw/apic.h | 9 ++++++++-
> hw/pc.c | 12 +++++++++++-
> target-i386/cpu.h | 27 ++++++++++++++++-----------
> target-i386/cpuid.c | 6 ++++++
> 5 files changed, 56 insertions(+), 38 deletions(-)
>
> diff --git a/hw/apic.c b/hw/apic.c
> index 91c8d93..332c66e 100644
> --- a/hw/apic.c
> +++ b/hw/apic.c
> @@ -95,7 +95,7 @@
> #define MSI_ADDR_SIZE 0x100000
>
> struct APICState {
> - CPUState *cpu_env;
> + void *cpu_env;
I proposed having an opaque CPUState type in hw/ but it was rejected.
But I don't think using a void pointer is any better.
Paolo
next prev parent reply other threads:[~2010-06-06 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 21:31 [Qemu-devel] [PATCH 6/6] apic: avoid using CPUState internals Blue Swirl
2010-06-06 7:36 ` [Qemu-devel] " Jan Kiszka
2010-06-06 7:42 ` Blue Swirl
2010-06-06 17:39 ` Paolo Bonzini [this message]
2010-06-07 6:35 ` Markus Armbruster
2010-06-09 19:59 ` Blue Swirl
2010-06-10 10:14 ` Paolo Bonzini
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=4C0BDD61.9020908@redhat.com \
--to=pbonzini@redhat.com \
--cc=blauwirbel@gmail.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).