From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [patch 2/2] machine struct - specify max_cpus at the per machine level
Date: Tue, 07 Oct 2008 15:40:03 -0500 [thread overview]
Message-ID: <48EBC923.2040203@codemonkey.ws> (raw)
In-Reply-To: <48EA0E7F.9090100@sgi.com>
Jes Sorensen wrote:
> Hi,
>
> This is the part that does the actual max_cpu support and checks.
> I have done my best to make it match what we had before with the old
> setup, but over time authors maintaining specific machines may want to
> adjust it.
Applied. Thanks.
Regards,
Anthony Liguori
> Cheers,
> Jes
>
next prev parent reply other threads:[~2008-10-07 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 13:11 [Qemu-devel] [patch 2/2] machine struct - specify max_cpus at the per machine level Jes Sorensen
2008-10-07 20:40 ` Anthony Liguori [this message]
2008-10-07 21:30 ` andrzej zaborowski
2008-10-08 13:40 ` Jes Sorensen
2008-10-09 2:05 ` andrzej zaborowski
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=48EBC923.2040203@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.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).