Thread (50 messages) 50 messages, 7 authors, 2016-03-18
DORMANTno replies
Revisions (2)
  1. v3 [diff vs current]
  2. v3 current

[PATCH v3 00/16] KVM: arm64: GICv3 ITS emulation

From: Peter Maydell <hidden>
Date: 2016-03-18 17:14:24
Also in: kvm, kvmarm

On 18 March 2016 at 09:40, Christoffer Dall [off-list ref] wrote:
On Mon, Mar 14, 2016 at 06:20:36PM +0000, Andre Przywara wrote:
quoted
Well, probably there is not so much difference. I was just wondering if
it would be easier to treat that data as an opaque blob.
But you are probably right that it would just mean the difference
between documenting the format or not.
Even ignoring the migrate-to-TCG case, you cannot treat it as a blob,
because you want to be able to migrate between KVM on kernel version X
and version Y.
You could require userspace to treat it as an opaque blob, and
transparently handle any version-upgrade within the kernel.
I think having it be documented-to-userspace ABI makes it
clearer that any format changes are a Big Deal, though.

thanks
-- PMM
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help