From: Avi Kivity <avi@qumranet.com>
To: Glauber Costa <gcosta@redhat.com>
Cc: kvm-devel@lists.sourceforge.net, Marcelo Tosatti <marcelo@kvack.org>
Subject: Re: use smp_cpus as lapic id
Date: Tue, 04 Mar 2008 10:40:23 +0200 [thread overview]
Message-ID: <47CD0AF7.30101@qumranet.com> (raw)
In-Reply-To: <47CC26A4.2070500@redhat.com>
Glauber Costa wrote:
> apic is not acpi, although they are acronyms. Due to a confusion of
> mine, those things were mixed, leading to a bug reported at
> https://sourceforge.net/tracker/index.php?func=detail&aid=1903732&group_id=180599&atid=893831
>
>
> This patch fixes it, by assigning smp_cpus instead of MAX_CPUS to
> lapic_id in the MP APIC tables.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-03-04 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 16:26 use smp_cpus as lapic id Glauber Costa
2008-03-04 8:40 ` Avi Kivity [this message]
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=47CD0AF7.30101@qumranet.com \
--to=avi@qumranet.com \
--cc=gcosta@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=marcelo@kvack.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