Displaying 7 results from an estimated 7 matches for "beywond".
Did you mean:
beyond
2014 Sep 18
5
Standardizing an MSR or other hypercall to get an RNG seed?
...s all hypervisors and
>> guests? That is, could we put something like "CrossHVPara\0"
>> somewhere in that range, where each hypervisor would be free to decide
>> exactly where it ends up?
>
> That's also possible, but extending the hypervisor CPUID range
> beywond 400000FFH is not officially sanctioned by Intel.
>
> Xen started doing that in order to expose both Hyper-V and Xen
> CPUID leaves, and KVM followed the practice.
>
Whoops.
Might Intel be willing to extend that range to 0x40000000 -
0x400fffff? And would Microsoft be okay with using...
2014 Sep 18
5
Standardizing an MSR or other hypercall to get an RNG seed?
...s all hypervisors and
>> guests? That is, could we put something like "CrossHVPara\0"
>> somewhere in that range, where each hypervisor would be free to decide
>> exactly where it ends up?
>
> That's also possible, but extending the hypervisor CPUID range
> beywond 400000FFH is not officially sanctioned by Intel.
>
> Xen started doing that in order to expose both Hyper-V and Xen
> CPUID leaves, and KVM followed the practice.
>
Whoops.
Might Intel be willing to extend that range to 0x40000000 -
0x400fffff? And would Microsoft be okay with using...
2014 Sep 18
0
Standardizing an MSR or other hypercall to get an RNG seed?
...is mechanism to work across all hypervisors and
> guests? That is, could we put something like "CrossHVPara\0"
> somewhere in that range, where each hypervisor would be free to decide
> exactly where it ends up?
That's also possible, but extending the hypervisor CPUID range
beywond 400000FFH is not officially sanctioned by Intel.
Xen started doing that in order to expose both Hyper-V and Xen
CPUID leaves, and KVM followed the practice.
Paolo
2014 Sep 18
4
Standardizing an MSR or other hypercall to get an RNG seed?
On Thu, Sep 18, 2014 at 10:42 AM, Nakajima, Jun <jun.nakajima at intel.com> wrote:
> On Thu, Sep 18, 2014 at 10:20 AM, KY Srinivasan <kys at microsoft.com> wrote:
>>
>>
>>> -----Original Message-----
>>> From: Paolo Bonzini [mailto:paolo.bonzini at gmail.com] On Behalf Of Paolo
>>> Bonzini
>>> Sent: Thursday, September 18, 2014 10:18
2014 Sep 18
4
Standardizing an MSR or other hypercall to get an RNG seed?
On Thu, Sep 18, 2014 at 10:42 AM, Nakajima, Jun <jun.nakajima at intel.com> wrote:
> On Thu, Sep 18, 2014 at 10:20 AM, KY Srinivasan <kys at microsoft.com> wrote:
>>
>>
>>> -----Original Message-----
>>> From: Paolo Bonzini [mailto:paolo.bonzini at gmail.com] On Behalf Of Paolo
>>> Bonzini
>>> Sent: Thursday, September 18, 2014 10:18
2014 Sep 18
3
Standardizing an MSR or other hypercall to get an RNG seed?
...ross all hypervisors and
>> guests? That is, could we put something like "CrossHVPara\0"
>> somewhere in that range, where each hypervisor would be free to
>> decide exactly where it ends up?
>
> That's also possible, but extending the hypervisor CPUID range beywond
> 400000FFH is not officially sanctioned by Intel.
>
> Xen started doing that in order to expose both Hyper-V and Xen CPUID
> leaves, and KVM followed the practice.
>
Whoops.
Might Intel be willing to extend that range to 0x40000000 - 0x400fffff? And would Microsoft be okay with...
2014 Sep 18
3
Standardizing an MSR or other hypercall to get an RNG seed?
...ross all hypervisors and
>> guests? That is, could we put something like "CrossHVPara\0"
>> somewhere in that range, where each hypervisor would be free to
>> decide exactly where it ends up?
>
> That's also possible, but extending the hypervisor CPUID range beywond
> 400000FFH is not officially sanctioned by Intel.
>
> Xen started doing that in order to expose both Hyper-V and Xen CPUID
> leaves, and KVM followed the practice.
>
Whoops.
Might Intel be willing to extend that range to 0x40000000 - 0x400fffff? And would Microsoft be okay with...