qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: 'Peter Maydell' <peter.maydell@linaro.org>,
	'Shlomo Pongratz' <shlomopongratz@gmail.com>,
	'QEMU Developers' <qemu-devel@nongnu.org>,
	'Shlomo Pongratz' <shlomo.pongratz@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v4] Use Aff1 with mpidr
Date: Mon, 15 Jun 2015 11:03:09 +0200	[thread overview]
Message-ID: <20150615110309.4feb442e@nial.brq.redhat.com> (raw)
In-Reply-To: <004f01d0a743$37e2eb10$a7a8c130$@samsung.com>

On Mon, 15 Jun 2015 11:13:52 +0300
Pavel Fedin <p.fedin@samsung.com> wrote:

>  Hello!
> 
> > For machine models to specify topology we would need a property
> > or properties on the QOM object for the machine model to set,
> 
>  On which object? There's no single object inside a machine model. Of course you can expose MP IDs of CPU objects as properties and set them, but isn't it more difficult than just changing one global before setting things up?
that's how we model it for x86 target, i.e. board sets apic-id property
of CPU's it  creates, and that's what I've suggested before (i.e. not a global for sure).

>  But, OK, this is just a MHO, and generally i don't object. If you think that your suggestion is architecturally better, do it. I'm out of arguments. :)
> 
> > (And we'd need to have the code to see if KVM
> > supported setting arbitrary MPIDR values, and fail if not.)
> 
>  I believe this is a different story.
> 
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
> 
> 
> 

      reply	other threads:[~2015-06-15  9:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 12:28 [Qemu-devel] [PATCH v4] Use Aff1 with mpidr Pavel Fedin
2015-06-12 15:16 ` Peter Maydell
2015-06-15  7:13   ` Pavel Fedin
2015-06-15  7:40     ` Peter Maydell
2015-06-15  8:13       ` Pavel Fedin
2015-06-15  9:03         ` Igor Mammedov [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=20150615110309.4feb442e@nial.brq.redhat.com \
    --to=imammedo@redhat.com \
    --cc=p.fedin@samsung.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shlomo.pongratz@huawei.com \
    --cc=shlomopongratz@gmail.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).