From: Pavel Fedin <p.fedin@samsung.com>
To: 'Marc Zyngier' <marc.zyngier@arm.com>,
'Christoffer Dall' <christoffer.dall@linaro.org>
Cc: kvm@vger.kernel.org, 'Andre Przywara' <andre.przywara@arm.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH] KVM: arm/arm64: Add VGICv3 save/restore API documentation
Date: Thu, 08 Oct 2015 15:28:40 +0300 [thread overview]
Message-ID: <009501d101c4$dde8e2e0$99baa8a0$@samsung.com> (raw)
In-Reply-To: <561641F5.4060202@arm.com>
Hello!
> Well, compatibility with GICv2 is the biggest mistake we made when
> designing the GICv3 architecture. And that's why our emulation doesn't
> give a damn about v2 compatibility.
Ok, i see your arguments, and after that it becomes a matter of personal taste. Three beat one, i
go your way. :) Don't know if i'll be able to roll out v5 tomorrow, but i think on monday i'll
definitely do.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
WARNING: multiple messages have this Message-ID (diff)
From: p.fedin@samsung.com (Pavel Fedin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM: arm/arm64: Add VGICv3 save/restore API documentation
Date: Thu, 08 Oct 2015 15:28:40 +0300 [thread overview]
Message-ID: <009501d101c4$dde8e2e0$99baa8a0$@samsung.com> (raw)
In-Reply-To: <561641F5.4060202@arm.com>
Hello!
> Well, compatibility with GICv2 is the biggest mistake we made when
> designing the GICv3 architecture. And that's why our emulation doesn't
> give a damn about v2 compatibility.
Ok, i see your arguments, and after that it becomes a matter of personal taste. Three beat one, i
go your way. :) Don't know if i'll be able to roll out v5 tomorrow, but i think on monday i'll
definitely do.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-10-08 12:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 19:50 [PATCH] KVM: arm/arm64: Add VGICv3 save/restore API documentation Christoffer Dall
2015-10-07 19:50 ` Christoffer Dall
2015-10-08 7:17 ` Pavel Fedin
2015-10-08 7:17 ` Pavel Fedin
2015-10-08 8:23 ` Christoffer Dall
2015-10-08 8:23 ` Christoffer Dall
2015-10-08 9:10 ` Pavel Fedin
2015-10-08 9:10 ` Pavel Fedin
2015-10-08 9:28 ` Christoffer Dall
2015-10-08 9:28 ` Christoffer Dall
2015-10-08 10:14 ` Marc Zyngier
2015-10-08 10:14 ` Marc Zyngier
2015-10-08 12:28 ` Pavel Fedin [this message]
2015-10-08 12:28 ` Pavel Fedin
2015-10-08 12:36 ` Christoffer Dall
2015-10-08 12:36 ` Christoffer Dall
2015-10-08 12:45 ` Pavel Fedin
2015-10-08 12:45 ` Pavel Fedin
2015-10-08 12:51 ` Marc Zyngier
2015-10-08 12:51 ` Marc Zyngier
2015-10-08 12:55 ` Peter Maydell
2015-10-08 12:55 ` Peter Maydell
2015-10-08 13:28 ` [Qemu-devel] " Pavel Fedin
2015-10-08 13:37 ` Peter Maydell
2015-10-08 14:29 ` Pavel Fedin
2015-10-08 10:25 ` Peter Maydell
2015-10-08 10:25 ` Peter Maydell
2015-10-09 7:30 ` Pavel Fedin
2015-10-09 7:30 ` Pavel Fedin
2015-10-09 8:06 ` Marc Zyngier
2015-10-09 8:06 ` Marc Zyngier
2015-10-09 8:10 ` Pavel Fedin
2015-10-09 8:10 ` Pavel Fedin
2015-10-09 8:29 ` Marc Zyngier
2015-10-09 8:29 ` Marc Zyngier
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='009501d101c4$dde8e2e0$99baa8a0$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=andre.przywara@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.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.