From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [patch] move MAX_CPUS to cpu.h
Date: Sat, 20 Sep 2008 00:14:17 +0000 [thread overview]
Message-ID: <48D44059.3060307@redhat.com> (raw)
In-Reply-To: <48D2665C.5090306@sgi.com>
Jes Sorensen wrote:
> Hi,
>
> I noticed that qemu-kvm.c hardcodes the array of struct vcpu_info
> to 256, instead of using the MAX_CPUS #define. This patch corrects
> this by moving the definition of MAX_CPUS to cpu.h from vl.c and
> then fixes qemu-kvm.c
This should be send to qemu-devel (without the kvm change), and after
the next merge we can fix qemu-kvm.c.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Jes Sorensen <jes@sgi.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
kvm@vger.kernel.org, kvm-ia64@vger.kernel.org
Subject: Re: [patch] move MAX_CPUS to cpu.h
Date: Fri, 19 Sep 2008 17:14:17 -0700 [thread overview]
Message-ID: <48D44059.3060307@redhat.com> (raw)
In-Reply-To: <48D2665C.5090306@sgi.com>
Jes Sorensen wrote:
> Hi,
>
> I noticed that qemu-kvm.c hardcodes the array of struct vcpu_info
> to 256, instead of using the MAX_CPUS #define. This patch corrects
> this by moving the definition of MAX_CPUS to cpu.h from vl.c and
> then fixes qemu-kvm.c
This should be send to qemu-devel (without the kvm change), and after
the next merge we can fix qemu-kvm.c.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-09-20 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 14:31 [patch] move MAX_CPUS to cpu.h Jes Sorensen
2008-09-18 14:31 ` Jes Sorensen
2008-09-20 0:14 ` Avi Kivity [this message]
2008-09-20 0:14 ` Avi Kivity
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=48D44059.3060307@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.