From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [patch] fold struct vcpu_info into CPUState
Date: Sun, 05 Oct 2008 10:02:41 +0000 [thread overview]
Message-ID: <48E890C1.407@redhat.com> (raw)
In-Reply-To: <48E0F318.7050303@sgi.com>
Jes Sorensen wrote:
> Hi,
>
> Trying to get rid of the static declaration of the vcpu_info array, this
> patch folds it into CPUState. I have only been able to test it on ia64,
> but it seems to behave as expect, however ia64 SMP support is still a
> bit flakey, so I would appreciate it if someone would test this on x86
> and PPC. It builds on x86_64 at least.
>
> Comments appreciated.
Looks reasonable to me. Glommer, please review this as well. Does this
help or interfere with your efforts?
--
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: kvm@vger.kernel.org, kvm-ia64@vger.kernel.org,
Glauber Costa <glommer@redhat.com>
Subject: Re: [patch] fold struct vcpu_info into CPUState
Date: Sun, 05 Oct 2008 12:02:41 +0200 [thread overview]
Message-ID: <48E890C1.407@redhat.com> (raw)
In-Reply-To: <48E0F318.7050303@sgi.com>
Jes Sorensen wrote:
> Hi,
>
> Trying to get rid of the static declaration of the vcpu_info array, this
> patch folds it into CPUState. I have only been able to test it on ia64,
> but it seems to behave as expect, however ia64 SMP support is still a
> bit flakey, so I would appreciate it if someone would test this on x86
> and PPC. It builds on x86_64 at least.
>
> Comments appreciated.
Looks reasonable to me. Glommer, please review this as well. Does this
help or interfere with your efforts?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-10-05 10:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 15:24 [patch] fold struct vcpu_info into CPUState Jes Sorensen
2008-09-29 15:24 ` Jes Sorensen
2008-10-05 10:02 ` Avi Kivity [this message]
2008-10-05 10:02 ` Avi Kivity
2008-10-05 20:48 ` Glauber Costa
2008-10-05 20:48 ` Glauber Costa
2008-10-13 22:24 ` Glauber Costa
2008-10-13 22:24 ` Glauber Costa
2008-10-17 15:28 ` Jes Sorensen
2008-10-17 15:28 ` Jes Sorensen
2008-10-17 21:27 ` Glauber Costa
2008-10-17 21:27 ` Glauber Costa
2008-10-24 15:57 ` Jes Sorensen
2008-10-24 15:57 ` Jes Sorensen
2008-10-24 19:10 ` Hollis Blanchard
2008-10-24 19:10 ` Hollis Blanchard
2008-10-27 9:48 ` Jes Sorensen
2008-10-27 9:48 ` Jes Sorensen
2008-10-27 16:02 ` Hollis Blanchard
2008-10-27 16:02 ` Hollis Blanchard
2008-10-27 16:06 ` Jes Sorensen
2008-10-27 16:06 ` Jes Sorensen
-- strict thread matches above, loose matches on Subject: below --
2008-10-28 16:25 [patch] v4 - " Jes Sorensen
2008-10-28 16:25 ` Jes Sorensen
2008-10-29 13:01 ` Anthony Liguori
2008-10-29 13:01 ` Anthony Liguori
2008-10-29 13:04 ` Jes Sorensen
2008-10-29 13:04 ` Jes Sorensen
2008-10-29 13:09 ` Anthony Liguori
2008-10-29 13:09 ` Anthony Liguori
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=48E890C1.407@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.