From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: zhugh.fnst@cn.fujitsu.com,
"Eduardo Habkost" <ehabkost@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Alexander Graf" <agraf@suse.de>,
"Bharata B Rao" <bharata@linux.vnet.ibm.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH v3 0/3] Bitmap based CPU enumeration
Date: Thu, 04 Jun 2015 10:51:35 +0200 [thread overview]
Message-ID: <55701197.4060200@redhat.com> (raw)
In-Reply-To: <CAEgOgz5yuyQtkhjFfWPZH-+HsaSM3F9PehGHfGzoJjp_GNtznA@mail.gmail.com>
On 04/06/2015 10:39, Peter Crosthwaite wrote:
>> > I wouldn't mind separating the "CPU" parts of exec.c and moving them
>> > under Andreas and Eduardo's mantainership. In fact, Peter, in your
>> > patch to move stuff from cpu-exec.c to cpus.c, perhaps you can use
>> > qom/cpu.c instead? Then qom/cpu.c can also be the place where we can
>> > move the CPU parts of exec.c.
>> >
> So that relocated code uses conditional compile based on
> CONFIG_SOFTMMU. Is that def accessible from common-obj-y code which
> qom/cpu.c is?
>
> My choice of cpus.c was based on the fact that it was obj-y.
Hmm, right---qom/cpu.c is indeed common-obj-y, so it has to be a new
file. cpu-exec.c is taken, so I guess I'll move the memory parts of
exec.c out to exec-memory.c and leave exec.c for the obj-y part of CPU
object handling. We have:
- cpu-exec.c: TCG only, arch-obj-y
- cpus.c: thread management, obj-y
- exec.c: CPU object management, obj-y
- qom/cpu.c: CPU object management, common-obj-y
And you can move the stuff from cpu-exec.c to exec.c in your patches.
> I assume this is all follow up work out of scope of Bharata's code. Do
> you have a queue I can rebase my conflicting ENV_GET_CPU work on?
No, I don't, because I'm not going to be the one who merge these
patches. Sorry.
Paolo
prev parent reply other threads:[~2015-06-04 8:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 5:02 [Qemu-devel] [PATCH v3 0/3] Bitmap based CPU enumeration Bharata B Rao
2015-05-21 5:02 ` [Qemu-devel] [PATCH v3 1/3] cpus: Add Error argument to cpu_exec_init() Bharata B Rao
2015-05-21 8:50 ` Igor Mammedov
2015-05-25 1:03 ` David Gibson
2015-05-29 5:02 ` Peter Crosthwaite
2015-05-21 5:02 ` [Qemu-devel] [PATCH v3 2/3] cpus: Convert cpu_index into a bitmap Bharata B Rao
2015-05-21 8:58 ` Igor Mammedov
2015-05-25 1:05 ` David Gibson
2015-05-29 5:15 ` Peter Crosthwaite
2015-05-21 5:02 ` [Qemu-devel] [PATCH v3 3/3] ppc: Move cpu_exec_init() call to realize function Bharata B Rao
2015-05-21 5:28 ` Andreas Färber
2015-05-21 5:37 ` Bharata B Rao
2015-05-21 9:05 ` Igor Mammedov
2015-05-21 10:18 ` Bharata B Rao
2015-05-21 11:24 ` Igor Mammedov
2015-05-29 5:17 ` Peter Crosthwaite
2015-05-29 7:33 ` Bharata B Rao
2015-05-29 2:27 ` [Qemu-devel] [PATCH v3 0/3] Bitmap based CPU enumeration Bharata B Rao
2015-05-29 4:59 ` Peter Crosthwaite
2015-06-04 3:08 ` Bharata B Rao
2015-06-04 5:44 ` Peter Crosthwaite
2015-06-04 8:09 ` Paolo Bonzini
2015-06-04 8:39 ` Peter Crosthwaite
2015-06-04 8:51 ` Paolo Bonzini [this message]
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=55701197.4060200@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=zhugh.fnst@cn.fujitsu.com \
/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).