All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: 'Shlomo Pongratz' <shlomopongratz@gmail.com>
Cc: peter.maydell@linaro.org, eric.auger@linaro.org,
	'Shlomo Pongratz' <shlomo.pongratz@huawei.com>,
	qemu-devel@nongnu.org, shannon.zhao@linaro.org,
	ashoks@broadcom.com, imammedo@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC V5 1/9] hw/intc: Implement GIC-500 support files
Date: Wed, 21 Oct 2015 15:32:03 +0300	[thread overview]
Message-ID: <013501d10bfc$7e0dc1f0$7a2945d0$@samsung.com> (raw)
In-Reply-To: <CAHzK-V2wNRDN7Y=ccYG3Pr_-SXfHXyQJh=W9A-fZDpOtD1whOA@mail.gmail.com>

 Hello!

>> See this: http://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg02349.html. This is also a part of my live migration RFC.
>> I remember that Peter told long time ago that "it should really be a property", when i integrated full affinity support. But, he currently
>> refused to accept this small standalone patch because there are no users for now. My GICv3 live migration is waiting for kernel API to be
>> ready. And kernel API is waiting for kernel 4.5 development cycle to begin.
> So please resubmit it and mention me as a client.

 Ok, i'll PING, but you can also include it into your patchset. BTW, why is it still RFC?

> But I wonder if accessing the property in real time (not in only in initialization) from the GIC code will have impact on performance.

 It can, but you can cache them during realize. For example, if you accept my data layout, then you can just add "uint64_t mp_affinity" to GICv3CPUState.

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia

  reply	other threads:[~2015-10-21 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1445396964-21189-1-git-send-email-shlomopongratz@gmail.com>
2015-10-21  6:48 ` [Qemu-devel] [PATCH RFC V5 1/9] hw/intc: Implement GIC-500 support files Pavel Fedin
     [not found]   ` <CAHzK-V0YsPx8E66fNpJ7C6T=tE-CM-pg2o5vQNpYn1SQ4BeLxg@mail.gmail.com>
2015-10-21 10:48     ` Pavel Fedin
2015-10-21 11:38       ` Shlomo Pongratz
2015-10-21 12:32         ` Pavel Fedin [this message]
2015-10-21 13:12           ` Shlomo Pongratz
2015-10-21 13:39             ` Pavel Fedin
2015-10-21 13:58               ` Shlomo Pongratz
2015-10-20 17:22 [Qemu-devel] [PATCH RFC V5 0/9] Implement GIC-500 from GICv3 family for arm64 Shlomo Pongratz
     [not found] ` <1445361732-16257-2-git-send-email-shlomopongratz@gmail.com>
2015-10-22 11:53   ` [Qemu-devel] [PATCH RFC V5 1/9] hw/intc: Implement GIC-500 support files Pavel Fedin

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='013501d10bfc$7e0dc1f0$7a2945d0$@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=ashoks@broadcom.com \
    --cc=eric.auger@linaro.org \
    --cc=imammedo@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shannon.zhao@linaro.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 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.