From: "Stanislav" <stlintel@gmail.com>
To: 'Glauber Costa' <glommer@redhat.com>
Cc: 'Jan Kiszka' <jan.kiszka@siemens.com>,
aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: RE: [Qemu-devel] Re: [PATCH 2/4] move CPUID_APIC flag to where it belongs
Date: Wed, 6 May 2009 20:43:09 +0300 [thread overview]
Message-ID: <000101c9ce72$201b6670$60523350$@com> (raw)
In-Reply-To: <20090506174136.GG26401@poweredge.glommer>
Local apic and i/o apic are not really related.
Local apic is actually a cpu feature, not optional external peripheral.
I/O apic is external hardware on board and if you don't have it - you can't
program your interrupts that much.
I am not telling if a patch is wrong/better than it was before - just want
to point out how it really works.
Stanislav
-----Original Message-----
From: Glauber Costa [mailto:glommer@redhat.com]
Sent: Wednesday, May 06, 2009 8:42 PM
To: Stanislav
Cc: 'Jan Kiszka'; aliguori@us.ibm.com; qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 2/4] move CPUID_APIC flag to where it
belongs
On Wed, May 06, 2009 at 08:29:23PM +0300, Stanislav wrote:
> If OS boot fine its more luck. The flag indicates presence of local apic,
> not "if it is supported".
> For example when lapic is globally disabled (i.e. not present) CPUID flag
is
> cleared off as well.
> But CPU is still supports lapic, after reset it will be back.
What if we take out a cpu that supports lapic, and is connected to an apic
system,
and connects it to a board that has no apic?
Also, note that in the old code, it was set regardless of the existance of
an APIC
anyway. The only dependancy was on smp_cpus > 1.
next prev parent reply other threads:[~2009-05-06 17:43 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
2009-05-06 17:29 ` Stanislav
2009-05-06 17:41 ` Glauber Costa
2009-05-06 17:43 ` Stanislav [this message]
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='000101c9ce72$201b6670$60523350$@com' \
--to=stlintel@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=glommer@redhat.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).