From: Pavel Fedin <p.fedin@samsung.com>
To: 'Christoffer Dall' <christoffer.dall@linaro.org>
Cc: 'Peter Maydell' <peter.maydell@linaro.org>,
'Marc Zyngier' <marc.zyngier@arm.com>,
kvmarm@lists.cs.columbia.edu, 'kvm-devel' <kvm@vger.kernel.org>
Subject: RE: [PATCH 3/3] KVM: arm64: Implement accessors for vGIC CPU interface registers
Date: Mon, 31 Aug 2015 14:49:46 +0300 [thread overview]
Message-ID: <018101d0e3e3$2285a690$6790f3b0$@samsung.com> (raw)
In-Reply-To: <20150831090321.GK24113@cbox>
Hello!
> I think it's worth moving the thing to device attributes, yes,
> especially given that I never expect us to trap and emulate GICv3 system
> register accesses from a guest in KVM. Is that correct?
Yes, but nevertheless, for GICv2 attributes we reuse the same code which is expected to trap MMIO
accesses from guest. And there we also have MMIO handlers for the CPU interface, which are also
never trapped from guest. So why cannot we do the same for GICv3 CPU interface, and simply reuse
existing APIs?
I am currently working on full support in qemu, and it's not difficult to deal with CPU fd's.
Because anyway you have to iterate through all VCPUs in order to save state correctly.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-08-31 11:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 12:56 [PATCH 0/3] KVM: arm64: Implement API for vGICv3 live migration Pavel Fedin
2015-08-28 12:56 ` [PATCH 1/3] KVM: arm64: Implement vGICv3 distributor and redistributor access from userspace Pavel Fedin
2015-08-30 16:42 ` Christoffer Dall
2015-08-31 7:35 ` Pavel Fedin
2015-08-31 8:59 ` Christoffer Dall
2015-09-01 13:52 ` Andre Przywara
2015-09-01 14:27 ` Pavel Fedin
2015-09-01 14:46 ` Peter Maydell
2015-08-28 12:56 ` [PATCH 2/3] KVM: arm64: Allow to use accessors in KVM_SET_ONE_REG and KVM_GET_ONE_REG Pavel Fedin
2015-08-28 12:56 ` [PATCH 3/3] KVM: arm64: Implement accessors for vGIC CPU interface registers Pavel Fedin
2015-08-30 16:50 ` Christoffer Dall
2015-08-30 18:39 ` Peter Maydell
2015-08-31 7:43 ` Pavel Fedin
2015-08-31 9:03 ` Christoffer Dall
2015-08-31 11:49 ` Pavel Fedin [this message]
2015-08-31 9:01 ` Christoffer Dall
2015-09-01 13:09 ` Pavel Fedin
2015-09-01 14:06 ` Christoffer Dall
2015-08-30 16:29 ` [PATCH 0/3] KVM: arm64: Implement API for vGICv3 live migration Christoffer Dall
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='018101d0e3e3$2285a690$6790f3b0$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=peter.maydell@linaro.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