[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALMp9eRLZO4Ou3W=1hJ93OyBp+-ykP4nefOSXeyZn-XePFBg+A@mail.gmail.com>
Date: Tue, 15 May 2018 14:55:17 -0700
From: Jim Mattson <jmattson@...gle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc: Wanpeng Li <kernellwp@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
kvm list <kvm@...r.kernel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Radim Krčmář <rkrcmar@...hat.com>,
Tim Shearer <tshearer@...aoptical.com>,
Liran Alon <liran.alon@...cle.com>
Subject: Re: [PATCH 1/3] KVM: VMX: Introduce per-VM I/O permission bitmaps
Since these pages are typically not used, can we allocate them conditionally?
On Fri, May 11, 2018 at 8:39 AM, Konrad Rzeszutek Wilk
<konrad.wilk@...cle.com> wrote:
>> /*
>> - * A vmexit (to either L1 hypervisor or L0 userspace) is always needed
>> - * for I/O port accesses.
>> + * Merging of IO bitmap not currently supported.
>
> s/not/is not/
>
> And with that
>
> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
>
> Thank you!
>> + * Rather, exit every time.
>> */
>> exec_control &= ~CPU_BASED_USE_IO_BITMAPS;
>> exec_control |= CPU_BASED_UNCOND_IO_EXITING;
>> --
>> 2.7.4
>>
Powered by blists - more mailing lists