From: David Gibson <david@gibson.dropbear.id.au>
To: groug@kaod.org
Cc: clg@kaod.org, qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv2 0/7] BROKEN, SORRY: Better handling of machine specific per-cpu information
Date: Thu, 14 Jun 2018 13:52:07 +1000 [thread overview]
Message-ID: <20180614035207.GK3042@umbus.fritz.box> (raw)
In-Reply-To: <20180614010446.30854-1-david@gibson.dropbear.id.au>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On Thu, Jun 14, 2018 at 11:04:39AM +1000, David Gibson wrote:
> It's moderately common for a machine type to need to keep track of
> information that is specific to the platform it implements, but
> per-cpu.
>
> While it could keep such information inside the MachineState, this
> makes lookup from the CPUState awkward. So, this series adds a
> standard way to stash machine-specific per-cpu information using a
> void pointer in the PowerPCCPU object. The machine is responsible for
> alloc()ing, free()ing and (if applicable) migrating this state.
>
> The meat of the series is the last two patches. The first 5 clean up
> a number of minor uglies I encountered while implementing.
Oops, realized 7/7 is totally broken on a KVM build. I'll send a new
spin.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-06-14 3:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 1:04 [Qemu-devel] [PATCHv2 0/7] Better handling of machine specific per-cpu information David Gibson
2018-06-14 1:04 ` [Qemu-devel] [PATCHv2 1/7] spapr: Clean up cpu realize/unrealize paths David Gibson
2018-06-14 1:04 ` [Qemu-devel] [PATCHv2 2/7] pnv: Fix some error handling cpu realize() David Gibson
2018-06-14 1:04 ` [Qemu-devel] [PATCHv2 3/7] pnv_core: Allocate cpu thread objects individually David Gibson
2018-06-14 1:04 ` [Qemu-devel] [PATCHv2 4/7] pnv: Clean up cpu realize path David Gibson
2018-06-14 1:04 ` [Qemu-devel] [PATCHv2 5/7] pnv: Add cpu unrealize path David Gibson
2018-06-14 1:04 ` [Qemu-devel] [PATCHv2 6/7] target/ppc: Replace intc pointer with a general machine_data pointer David Gibson
2018-06-14 1:04 ` [Qemu-devel] [PATCHv2 7/7] target/ppc, spapr: Move VPA information to machine_data David Gibson
2018-06-14 3:52 ` David Gibson [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=20180614035207.GK3042@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).