Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1531571 > unrolled thread
| Started by | David Matlack <dmatlack@google.com> |
|---|---|
| First post | 2016-11-28 21:00 +0100 |
| Last post | 2016-11-28 21:00 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 2/4] KVM: nVMX: fix checks on CR{0,4} during virtual VMX operation David Matlack <dmatlack@google.com> - 2016-11-28 21:00 +0100
| From | David Matlack <dmatlack@google.com> |
|---|---|
| Date | 2016-11-28 21:00 +0100 |
| Subject | Re: [PATCH 2/4] KVM: nVMX: fix checks on CR{0,4} during virtual VMX operation |
| Message-ID | <sIAfM-6sT-23@gated-at.bofh.it> |
On Wed, Nov 23, 2016 at 3:31 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 23/11/2016 02:14, David Matlack wrote:
>> +static bool fixed_bits_valid(u64 val, u64 fixed0, u64 fixed1)
>> +{
>> + return ((val & fixed0) == fixed0) && ((~val & ~fixed1) == ~fixed1);
>> +}
>> +
>
> This is the same as vmx_control_verify (except with u64 arguments
> instead of u32).
Good point. I'll remove this duplication in v3.
Back to top | Article view | linux.kernel
csiph-web