[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02039a7b-01b4-ea5c-bd73-100ea753bf5e@redhat.com>
Date: Mon, 20 Apr 2020 23:09:47 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Jon Cargille <jcargill@...gle.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>
Cc: David Matlack <dmatlack@...gle.com>,
Sean Christopherson <sean.j.christopherson@...el.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kvm: add capability for halt polling
On 20/04/20 20:47, Jon Cargille wrote:
>> Is it safe to allow any value from userspace here or would it maybe make
>> sense to only allow [0, global halt_poll_ns]?
> I believe that any value is safe; a very large value effectively disables
> halt-polling, which is equivalent to setting a value of zero to explicitly
> disable it, which is legal.
Doesn't a large value make KVM poll all the time? But you could do that
just by running "for (;;)" so there's no reason to limit the parameter.
Paolo
Powered by blists - more mailing lists