qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Jones <drjones@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Lieven <pl@kamp.de>, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] vl: smp_parse sanity checks
Date: Tue, 11 Nov 2014 12:15:26 +0100	[thread overview]
Message-ID: <5461EFCE.8010104@redhat.com> (raw)
In-Reply-To: <1415376280-14130-1-git-send-email-drjones@redhat.com>



On 07/11/2014 17:04, Andrew Jones wrote:
> See individual patches.
> 
> Andrew Jones (3):
>   vl: fix max_cpus check
>   vl: sanity check cpu topology
>   vl: warn on topology <-> maxcpus mismatch
> 
>  vl.c | 38 ++++++++++++++++++++++++++++++++------
>  1 file changed, 32 insertions(+), 6 deletions(-)
> 

Looks good, but Eduardo should be the authority on this stuff.

Adding Peter Lieven too, because he looked at bad -smp configurations
too in the past.

Paolo

  parent reply	other threads:[~2014-11-11 11:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07 16:04 [Qemu-devel] [PATCH 0/3] vl: smp_parse sanity checks Andrew Jones
2014-11-07 16:04 ` [Qemu-devel] [PATCH 1/3] vl: fix max_cpus check Andrew Jones
2014-11-07 16:58   ` Eduardo Habkost
2014-11-07 16:04 ` [Qemu-devel] [PATCH 2/3] vl: sanity check cpu topology Andrew Jones
2014-11-11 12:41   ` Eduardo Habkost
2014-11-11 14:37     ` Andrew Jones
2014-11-11 15:48       ` Eduardo Habkost
2014-11-11 17:04         ` Andrew Jones
2014-11-11 17:27           ` Eduardo Habkost
2014-11-11 18:31       ` Eduardo Habkost
2014-11-12  9:14         ` Andrew Jones
2014-11-07 16:04 ` [Qemu-devel] [PATCH 3/3] vl: warn on topology <-> maxcpus mismatch Andrew Jones
2014-11-11 11:15 ` Paolo Bonzini [this message]
2014-11-11 12:42   ` [Qemu-devel] [PATCH 0/3] vl: smp_parse sanity checks Eduardo Habkost

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=5461EFCE.8010104@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=drjones@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=pl@kamp.de \
    --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).