All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Haiwei Li <lihaiwei.kernel@gmail.com>,
	kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	Jim Mattson <jmattson@google.com>,
	Haiwei Li <lihaiwei@tencent.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] Revert "KVM: Check the allocation of pv cpu mask"
Date: Wed, 16 Sep 2020 13:04:43 +0200	[thread overview]
Message-ID: <87een2htis.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <6c2204ad-590b-025d-f728-0e6e67bf24ba@gmail.com>

Haiwei Li <lihaiwei.kernel@gmail.com> writes:

> On 20/9/16 17:03, Vitaly Kuznetsov wrote:
>> The commit 0f990222108d ("KVM: Check the allocation of pv cpu mask") we
>> have in 5.9-rc5 has two issue:
>> 1) Compilation fails for !CONFIG_SMP, see:
>>     https://bugzilla.kernel.org/show_bug.cgi?id=209285
>> 
>> 2) This commit completely disables PV TLB flush, see
>>     https://lore.kernel.org/kvm/87y2lrnnyf.fsf@vitty.brq.redhat.com/
>> 
>> The allocation problem is likely a theoretical one, if we don't
>> have memory that early in boot process we're likely doomed anyway.
>> Let's solve it properly later.
>
> Hi, i have sent a patchset to fix this commit.
>
> https://lore.kernel.org/kvm/20200914091148.95654-1-lihaiwei.kernel@gmail.com/T/#m6c27184012ee5438e5d91c09b1ba1b6a3ee30ee4
>
> What do you think?

Saw it, looks good to me. We are, however, already very, very late in 5.9
release cycle and the original issue you were addressing (allocation
failure) is likely a theoretical only I suggest we just revert it before
5.9 is released. For 5.9 we can certainly take your PATCH2 merged with
0f99022210.

This Paolo's call anyway)

-- 
Vitaly


  reply	other threads:[~2020-09-16 19:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16  9:03 [PATCH] Revert "KVM: Check the allocation of pv cpu mask" Vitaly Kuznetsov
2020-09-16  9:29 ` Haiwei Li
2020-09-16 11:04   ` Vitaly Kuznetsov [this message]
2020-09-16 11:25     ` Haiwei Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87een2htis.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=lihaiwei.kernel@gmail.com \
    --cc=lihaiwei@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sean.j.christopherson@intel.com \
    --cc=wanpengli@tencent.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.