From: Glauber Costa <glommer@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 2/4] move CPUID_APIC flag to where it belongs
Date: Wed, 6 May 2009 12:51:41 -0300 [thread overview]
Message-ID: <20090506155141.GE26401@poweredge.glommer> (raw)
In-Reply-To: <4A01AF78.7050102@siemens.com>
On Wed, May 06, 2009 at 05:40:40PM +0200, Jan Kiszka wrote:
> Glauber Costa wrote:
> > We can safely do that inconditionally, so move to processor defined
> > flags like any other flag.
> >
> > Signed-off-by: Glauber Costa <glommer@redhat.com>
> > ---
> > hw/pc.c | 4 ----
> > target-i386/helper.c | 2 +-
> > 2 files changed, 1 insertions(+), 5 deletions(-)
> >
> > diff --git a/hw/pc.c b/hw/pc.c
> > index 351de83..b726c17 100644
> > --- a/hw/pc.c
> > +++ b/hw/pc.c
> > @@ -851,10 +851,6 @@ static void pc_init1(ram_addr_t ram_size, int vga_ram_size,
> > }
> > if (i != 0)
> > env->halted = 1;
> > - if (smp_cpus > 1) {
> > - /* XXX: enable it in all cases */
> > - env->cpuid_features |= CPUID_APIC;
> > - }
> > if (pci_enabled) {
> > apic_init(env);
> > }
> > diff --git a/target-i386/helper.c b/target-i386/helper.c
> > index 2210412..2c11cd3 100644
> > --- a/target-i386/helper.c
> > +++ b/target-i386/helper.c
> > @@ -102,7 +102,7 @@ typedef struct x86_def_t {
> > char model_id[48];
> > } x86_def_t;
> >
> > -#define I486_FEATURES (CPUID_FP87 | CPUID_VME | CPUID_PSE)
> > +#define I486_FEATURES (CPUID_FP87 | CPUID_VME | CPUID_PSE | CPUID_APIC)
>
> Without doing my homework:
> What impact will it have on an emulated CPUs without [L]APIC? I'm
> thinking of -M isapc e.g.
I tried, and it still boots fine.
The flag just indicates it supports an apic, not that it has one.
next prev parent reply other threads:[~2009-05-06 15:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 14:49 [Qemu-devel] [PATCH 0/4] Simplify cpu initialization Glauber Costa
2009-05-06 14:49 ` [Qemu-devel] [PATCH 1/4] move registering of cpu_reset to inside cpu_init Glauber Costa
2009-05-06 14:49 ` [Qemu-devel] [PATCH 2/4] move CPUID_APIC flag to where it belongs Glauber Costa
2009-05-06 14:49 ` [Qemu-devel] [PATCH 3/4] move halted state setting to inside of cpu_x86_init Glauber Costa
2009-05-06 14:49 ` [Qemu-devel] [PATCH 4/4] move apic functions to a separate apic.h header Glauber Costa
2009-05-06 15:52 ` [Qemu-devel] " Jan Kiszka
2009-05-06 16:08 ` Glauber Costa
2009-05-06 15:45 ` [Qemu-devel] Re: [PATCH 3/4] move halted state setting to inside of cpu_x86_init Jan Kiszka
2009-05-06 19:31 ` [Qemu-devel] " Blue Swirl
2009-05-06 21:42 ` Glauber Costa
2009-05-06 15:40 ` [Qemu-devel] Re: [PATCH 2/4] move CPUID_APIC flag to where it belongs Jan Kiszka
2009-05-06 15:51 ` Glauber Costa [this message]
2009-05-06 17:29 ` Stanislav
2009-05-06 17:41 ` Glauber Costa
2009-05-06 17:43 ` Stanislav
2009-05-06 18:17 ` Anthony Liguori
2009-05-06 17:02 ` [Qemu-devel] Re: [PATCH 1/4] move registering of cpu_reset to inside cpu_init Jan Kiszka
2009-05-06 19:36 ` [Qemu-devel] " Blue Swirl
2009-05-06 21:45 ` Glauber Costa
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=20090506155141.GE26401@poweredge.glommer \
--to=glommer@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.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).