qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Liu Yu <yu.liu@freescale.com>
Cc: kvm-ppc@vger.kernel.org, hollisb@us.ibm.com,
	qemu-devel@nongnu.org, aurelien@aurel32.net
Subject: [Qemu-devel] Re: [PATCH 1/5] kvm/powerpc: Enable MPIC for E500 platform.
Date: Thu, 26 Feb 2009 20:47:18 +0200	[thread overview]
Message-ID: <f43fc5580902261047q3080fb72k2e7a3855ca1b7a14@mail.gmail.com> (raw)
In-Reply-To: <1235644545-20816-2-git-send-email-yu.liu@freescale.com>

On 2/26/09, Liu Yu <yu.liu@freescale.com> wrote:
> MPIC and OpenPIC have very similar design.
>  So a lot of code can be reused.
>
>  Modification mainly include:
>  1. keep struct openpic_t to the maximum size of both MPIC and OpenPIC.
>  2. endianess swap.
>    MPIC has the same endianess as target, so no need to swap for MPIC.
>  3. using different init functions and function pointers for reset and irq raise.
>
>  Haven't test OpenPIC.
>
>  Signed-off-by: Liu Yu <yu.liu@freescale.com>

>  +    struct {
>  +        CPUReadMemoryFunc **read;
>  +        CPUWriteMemoryFunc **write;
>  +        target_phys_addr_t start_addr;
>  +        ram_addr_t size;
>  +    } list[] = {
>  +        {mpic_glb_read, mpic_glb_write, MPIC_GLB_REG_START, MPIC_GLB_REG_SIZE},
>  +        {mpic_tmr_read, mpic_tmr_write, MPIC_TMR_REG_START, MPIC_TMR_REG_SIZE},
>  +        {mpic_ext_read, mpic_ext_write, MPIC_EXT_REG_START, MPIC_EXT_REG_SIZE},
>  +        {mpic_int_read, mpic_int_write, MPIC_INT_REG_START, MPIC_INT_REG_SIZE},
>  +        {mpic_msg_read, mpic_msg_write, MPIC_MSG_REG_START, MPIC_MSG_REG_SIZE},
>  +        {mpic_msi_read, mpic_msi_write, MPIC_MSI_REG_START, MPIC_MSI_REG_SIZE},
>  +        {mpic_cpu_read, mpic_cpu_write, MPIC_CPU_REG_START, MPIC_CPU_REG_SIZE},
>  +    };

"static const" ?

  parent reply	other threads:[~2009-02-26 18:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26 10:35 [Qemu-devel] [PATCH v4 0/5] powerpc/kvm: Add MPC8544DS board support Liu Yu
2009-02-26 10:35 ` [Qemu-devel] [PATCH 1/5] kvm/powerpc: Enable MPIC for E500 platform Liu Yu
2009-02-26 10:35   ` [Qemu-devel] [PATCH 2/5] kvm/powerpc: Add freescale pci controller's support Liu Yu
2009-02-26 10:35     ` [Qemu-devel] [PATCH 3/5] kvm/powerpc: Add irq support for E500 core Liu Yu
2009-02-26 10:35       ` [Qemu-devel] [PATCH 4/5] kvm/powerpc: Add MPC8544DS board support Liu Yu
2009-02-26 10:35         ` [Qemu-devel] [PATCH 5/5] kvm/powerpc: flat device tree files for MPC8544DS Liu Yu
2009-02-26 16:21           ` [Qemu-devel] " Hollis Blanchard
2009-02-26 16:18         ` [Qemu-devel] Re: [PATCH 4/5] kvm/powerpc: Add MPC8544DS board support Hollis Blanchard
2009-02-26 18:47   ` Blue Swirl [this message]
2009-02-27  2:00     ` [Qemu-devel] RE: [PATCH 1/5] kvm/powerpc: Enable MPIC for E500 platform Liu Yu-B13201
2009-02-27 20:04       ` [Qemu-devel] " Blue Swirl
2009-03-02 16:42         ` Aurelien Jarno
2009-03-02 16:42 ` [Qemu-devel] Re: [PATCH v4 0/5] powerpc/kvm: Add MPC8544DS board support Aurelien Jarno

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=f43fc5580902261047q3080fb72k2e7a3855ca1b7a14@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=aurelien@aurel32.net \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=yu.liu@freescale.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).