search for: amluto

Andy Lutomirski writes ("[Xen-devel] [RFC] Hypervisor RNG and enumeration"): > Here's a draft CommonHV spec. It's also on github: > https://github.com/amluto/CommonHV This a worthwhile direction to investigate, and an interesting proposal. From a Xen point of view I have some concerns, though. I think in Xen we would want to implement the bulk of the provision of random numbers to guests outside the hypervisor. That is, the hypervisor itself should...

Here's a draft CommonHV spec. It's also on github: https://github.com/amluto/CommonHV So far, this provides a two-way RNG interface, a way to detect it, and a way to detect other hypervisor leaves. The latter is because, after both the enormous public thread and some private discussions, it seems that detection of existing CPUID paravirt leaves is annoying and inefficient...

Here's a draft CommonHV spec. It's also on github: https://github.com/amluto/CommonHV So far, this provides a two-way RNG interface, a way to detect it, and a way to detect other hypervisor leaves. The latter is because, after both the enormous public thread and some private discussions, it seems that detection of existing CPUID paravirt leaves is annoying and inefficient...

On Oct 29, 2014 8:17 AM, "Ian Jackson" <Ian.Jackson at eu.citrix.com> wrote: > > Andy Lutomirski writes ("[Xen-devel] [RFC] Hypervisor RNG and enumeration"): > > Here's a draft CommonHV spec. It's also on github: > > https://github.com/amluto/CommonHV > > This a worthwhile direction to investigate, and an interesting > proposal. From a Xen point of view I have some concerns, though. > > I think in Xen we would want to implement the bulk of the provision of > random numbers to guests outside the hypervisor. That is, t...

On Oct 29, 2014 8:17 AM, "Ian Jackson" <Ian.Jackson at eu.citrix.com> wrote: > > Andy Lutomirski writes ("[Xen-devel] [RFC] Hypervisor RNG and enumeration"): > > Here's a draft CommonHV spec. It's also on github: > > https://github.com/amluto/CommonHV > > This a worthwhile direction to investigate, and an interesting > proposal. From a Xen point of view I have some concerns, though. > > I think in Xen we would want to implement the bulk of the provision of > random numbers to guests outside the hypervisor. That is, t...

On 29/10/14 05:19, Andy Lutomirski wrote: > Here's a draft CommonHV spec. It's also on github: > > https://github.com/amluto/CommonHV > > So far, this provides a two-way RNG interface, a way to detect it, and > a way to detect other hypervisor leaves. The latter is because, after > both the enormous public thread and some private discussions, it seems > that detection of existing CPUID paravirt leaves is...

On 29/10/14 05:19, Andy Lutomirski wrote: > Here's a draft CommonHV spec. It's also on github: > > https://github.com/amluto/CommonHV > > So far, this provides a two-way RNG interface, a way to detect it, and > a way to detect other hypervisor leaves. The latter is because, after > both the enormous public thread and some private discussions, it seems > that detection of existing CPUID paravirt leaves is...

This switches virtio to use the DMA API unconditionally. I'm sure it breaks things, but it seems to work on x86 using virtio-pci, with and without Xen, and using both the modern 1.0 variant and the legacy variant. Changes from v2: - Fix really embarrassing bug. This version actually works. Changes from v1: - Fix an endian conversion error causing a BUG to hit. - Fix a DMA ordering issue

This switches virtio to use the DMA API unconditionally. I'm sure it breaks things, but it seems to work on x86 using virtio-pci, with and without Xen, and using both the modern 1.0 variant and the legacy variant. Changes from v2: - Fix really embarrassing bug. This version actually works. Changes from v1: - Fix an endian conversion error causing a BUG to hit. - Fix a DMA ordering issue