From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [patch] remove vcpu_info array v5
Date: Tue, 11 Nov 2008 09:26:56 +0000 [thread overview]
Message-ID: <49194FE0.4030003@redhat.com> (raw)
In-Reply-To: <4909C00F.8050704@sgi.com>
Jes Sorensen wrote:
> Avi Kivity wrote:
>> The code I mentioned only runs if the -no-kvm-irqchip option is
>> passed. It's not the highest performing option...
>
> What I meant was that I was able to compile the code, and there was only
> one piece left that needed that function, which is why I moved it and
> made it static in the acpi code.
>
That's because there is another static array in acpi.c...
>> So this isn't used a lot. But cpus definitely use cpu numbers (as
>> apic ids), so qemu needs to be prepared to handle this. As to
>> scalability, that takes will take a lot more work than
>> removing/changing arbitrary limits. Look at qemu_mutex and weep.
>
> Well we have to start somewhere. Just because there's limits in other
> areas too, doesn't mean we should discard valid improvements elsewhere.
> I'll get to some of that at some point, but there's soo many cards used
> to build this house....
Your patch builds the 16383rd floor while ignoring the 15th. Qemu
scaling issues are much, much more painful than what you were addressing.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Jes Sorensen <jes@sgi.com>
Cc: Glauber Costa <glommer@gmail.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Hollis Blanchard <hollisb@us.ibm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>
Subject: Re: [patch] remove vcpu_info array v5
Date: Tue, 11 Nov 2008 11:26:56 +0200 [thread overview]
Message-ID: <49194FE0.4030003@redhat.com> (raw)
In-Reply-To: <49185A12.9000105@sgi.com>
Jes Sorensen wrote:
> Avi Kivity wrote:
>> The code I mentioned only runs if the -no-kvm-irqchip option is
>> passed. It's not the highest performing option...
>
> What I meant was that I was able to compile the code, and there was only
> one piece left that needed that function, which is why I moved it and
> made it static in the acpi code.
>
That's because there is another static array in acpi.c...
>> So this isn't used a lot. But cpus definitely use cpu numbers (as
>> apic ids), so qemu needs to be prepared to handle this. As to
>> scalability, that takes will take a lot more work than
>> removing/changing arbitrary limits. Look at qemu_mutex and weep.
>
> Well we have to start somewhere. Just because there's limits in other
> areas too, doesn't mean we should discard valid improvements elsewhere.
> I'll get to some of that at some point, but there's soo many cards used
> to build this house....
Your patch builds the 16383rd floor while ignoring the 15th. Qemu
scaling issues are much, much more painful than what you were addressing.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-11-11 9:26 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 14:09 [patch] remove vcpu_info array v5 Jes Sorensen
2008-10-30 14:09 ` Jes Sorensen
2008-11-04 11:54 ` Avi Kivity
2008-11-04 11:54 ` Avi Kivity
2008-11-04 13:55 ` Glauber Costa
2008-11-04 13:55 ` Glauber Costa
2008-11-04 14:30 ` Avi Kivity
2008-11-04 14:30 ` Avi Kivity
2008-11-04 14:35 ` Glauber Costa
2008-11-04 14:35 ` Glauber Costa
2008-11-04 14:40 ` Avi Kivity
2008-11-04 14:40 ` Avi Kivity
2008-11-04 14:43 ` Glauber Costa
2008-11-04 14:43 ` Glauber Costa
2008-11-04 14:47 ` Avi Kivity
2008-11-04 14:47 ` Avi Kivity
2008-11-10 12:30 ` Jes Sorensen
2008-11-10 12:30 ` Jes Sorensen
2008-11-10 13:24 ` Jes Sorensen
2008-11-10 13:24 ` Jes Sorensen
2008-11-10 13:30 ` Jes Sorensen
2008-11-10 13:30 ` Jes Sorensen
2008-11-10 13:40 ` Avi Kivity
2008-11-10 13:40 ` Avi Kivity
2008-11-10 13:48 ` Avi Kivity
2008-11-10 13:48 ` Avi Kivity
2008-11-10 15:22 ` Anthony Liguori
2008-11-10 15:22 ` Anthony Liguori
2008-11-10 15:45 ` Avi Kivity
2008-11-10 15:45 ` Avi Kivity
2008-11-10 15:47 ` Jes Sorensen
2008-11-10 15:47 ` Jes Sorensen
2008-11-10 15:54 ` Avi Kivity
2008-11-10 15:54 ` Avi Kivity
2008-11-10 15:58 ` Jes Sorensen
2008-11-10 15:58 ` Jes Sorensen
2008-11-11 9:26 ` Avi Kivity [this message]
2008-11-11 9:26 ` Avi Kivity
2008-11-12 13:02 ` Jes Sorensen
2008-11-12 13:02 ` Jes Sorensen
2008-11-12 13:09 ` Glauber Costa
2008-11-12 13:09 ` Glauber Costa
2008-11-12 13:12 ` Avi Kivity
2008-11-12 13:12 ` Avi Kivity
2008-11-12 13:14 ` Avi Kivity
2008-11-12 13:14 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-11-13 16:46 [patch] pass opague CPUState through libkvm instead of int vcpu Jes Sorensen
2008-11-13 16:46 ` Jes Sorensen
2008-11-18 12:55 ` Avi Kivity
2008-11-18 12:55 ` Avi Kivity
2008-11-18 12:59 ` Jes Sorensen
2008-11-18 12:59 ` Jes Sorensen
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=49194FE0.4030003@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.