linux-kernel - Re: [PATCH v5 6/6] KVM: nVMX: Enable nested posted interrupt processing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACzj_yV8K+3aQJ6kf3f-25BVVoRqso2ay90kEyM7nx11e6=QMw@mail.gmail.com>
Date:	Tue, 3 Feb 2015 22:18:43 +0800
From:	Wincy Van <fanwenyi0529@...il.com>
To:	Paolo Bonzini <pbonzini@...hat.com>
Cc:	"gleb@...nel.org" <gleb@...nel.org>,
	"Zhang, Yang Z" <yang.z.zhang@...el.com>,
	"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Wanpeng Li <wanpeng.li@...ux.intel.com>,
	Jan Kiszka <jan.kiszka@....de>
Subject: Re: [PATCH v5 6/6] KVM: nVMX: Enable nested posted interrupt processing

On Tue, Feb 3, 2015 at 10:02 PM, Paolo Bonzini <pbonzini@...hat.com> wrote:
>
>
> On 03/02/2015 10:17, Wincy Van wrote:
>> +static int vmx_accomp_nested_posted_interrupt(struct kvm_vcpu *vcpu)
>
> Replace accomp with complete.

Will do.

>
>> +{
>> +       struct vcpu_vmx *vmx = to_vmx(vcpu);
>> +       int max_irr;
>> +       void *vapic_page;
>> +       u16 status;
>> +
>> +       if (vmx->nested.posted_intr_nv != -1 &&
>
> Testing posted_intr_nv is not necessary.
>

Indeed.

>> +           vmx->nested.pi_desc &&
>> +           vmx->nested.accomp_pir) {
>
> Replace accomp_pir with pi_pending.
>

Will do.

> The patch has corrupted spaces and tabs like the others, too.
>

I'm sorry, may I resend them via qq.com with the same version(v5) and
make the changes above?


Thanks,
Wincy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/