From: Gleb Natapov <gleb@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: aliguori@us.ibm.com, ehabkost@redhat.com, jan.kiszka@siemens.com,
mtosatti@redhat.com, mdroth@linux.vnet.ibm.com,
qemu-devel@nongnu.org, blauwirbel@gmail.com, avi@redhat.com,
pbonzini@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v2] MP initialization protocol differs between cpu families, and for P6 and onward models it is up to CPU to decide if it will be BSP using this protocol, so try to model this. However there is no point in implementing MP initialization protocol in qemu. Thus first CPU is always marked as BSP.
Date: Mon, 23 Jul 2012 11:06:48 +0300 [thread overview]
Message-ID: <20120723080648.GS26120@redhat.com> (raw)
In-Reply-To: <500D00C5.7090003@redhat.com>
On Mon, Jul 23, 2012 at 09:44:05AM +0200, Igor Mammedov wrote:
> Hello Gleb,
>
> Is this v2 patch more acceptable then v1?
Yes. Sorry for not being explicit about it :)
--
Gleb.
next prev parent reply other threads:[~2012-07-23 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 13:15 [Qemu-devel] [PATCH 0/2 v2] target-i386: refactor reset handling and move it into cpu.c Igor Mammedov
2012-07-10 13:15 ` [Qemu-devel] [PATCH 1/2] target-i386: move cpu halted decision into x86_cpu_reset Igor Mammedov
2012-07-12 6:38 ` Gleb Natapov
2012-07-12 13:09 ` Igor Mammedov
2012-07-12 13:22 ` [Qemu-devel] [PATCH v2] MP initialization protocol differs between cpu families, and for P6 and onward models it is up to CPU to decide if it will be BSP using this protocol, so try to model this. However there is no point in implementing MP initialization protocol in qemu. Thus first CPU is always marked as BSP Igor Mammedov
2012-07-23 7:44 ` Igor Mammedov
2012-07-23 8:06 ` Gleb Natapov [this message]
2012-07-23 11:02 ` Andreas Färber
2012-07-10 13:15 ` [Qemu-devel] [PATCH 2/2] target-i386: move cpu_reset and reset callback to cpu.c Igor Mammedov
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=20120723080648.GS26120@redhat.com \
--to=gleb@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.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).