All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	Alistair Francis <alistair23@gmail.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Konstanty Bialkowski <konstanty@ieee.org>
Subject: Re: [Qemu-devel] [PATCH v1 1/1] target_arm: Make the reset rom_ptr a property
Date: Thu, 21 Aug 2014 12:55:50 +0200	[thread overview]
Message-ID: <53F5D036.9010005@suse.de> (raw)
In-Reply-To: <CAEgOgz7vVSp2R_0za4pMzSKWx91ZLXUnXV2qo=G2Q+xgmKBLAg@mail.gmail.com>

Am 21.08.2014 05:37, schrieb Peter Crosthwaite:
> On Thu, Aug 21, 2014 at 11:40 AM, Alistair Francis <alistair23@gmail.com> wrote:
>> On Thu, Aug 21, 2014 at 11:36 AM, Alistair Francis <alistair23@gmail.com> wrote:
>>> diff --git a/target-arm/cpu-qom.h b/target-arm/cpu-qom.h
>>> index 07f3c9e..7e415f5 100644
>>> --- a/target-arm/cpu-qom.h
>>> +++ b/target-arm/cpu-qom.h
>>> @@ -138,6 +138,7 @@ typedef struct ARMCPU {
>>>      uint32_t id_isar3;
>>>      uint32_t id_isar4;
>>>      uint32_t id_isar5;
>>> +    uint32_t rom_address;
> 
> Any reason for this to go in amongst the ID register fields? It seems
> in a class of its own, and the closest thing to it would be rvbar
> which is down the bottom. My gut says it should be last field in the
> struct.

Whether it is zero'ed on reset here would be another concern.

Regards,
Andreas

>>>      uint64_t id_aa64pfr0;
>>>      uint64_t id_aa64pfr1;
>>>      uint64_t id_aa64dfr0;
[snip]

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  parent reply	other threads:[~2014-08-21 10:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21  1:36 [Qemu-devel] [PATCH v1 1/1] target_arm: Make the reset rom_ptr a property Alistair Francis
2014-08-21  1:40 ` Alistair Francis
2014-08-21  3:37   ` Peter Crosthwaite
2014-08-21  4:13     ` Alistair Francis
2014-08-21 10:55     ` Andreas Färber [this message]
2014-08-21 12:33     ` Peter Maydell
2014-08-21 12:37       ` Peter Crosthwaite
2014-08-21 12:40         ` Peter Maydell
2014-08-21 12:43           ` Peter Crosthwaite
2014-08-21 13:15       ` Christopher Covington
2014-08-21 13:18         ` Peter Maydell
2014-08-21  8:01 ` Peter Maydell
2014-08-21  8:35   ` Alistair Francis
2014-08-21  9:14     ` Peter Maydell
2014-08-21 12:09       ` Alistair Francis
2014-08-21 12:22         ` Peter Crosthwaite
2014-08-21 12:26           ` Alistair Francis
2014-08-21 12:24         ` Peter Maydell
2014-08-21 12:35           ` Peter Crosthwaite
2014-08-21 12:37           ` Alistair Francis

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=53F5D036.9010005@suse.de \
    --to=afaerber@suse.de \
    --cc=alistair23@gmail.com \
    --cc=konstanty@ieee.org \
    --cc=peter.crosthwaite@xilinx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.