From: Sasha Levin <sashal@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
stable@vger.kernel.org, Joerg Roedel <jroedel@suse.de>
Subject: Re: [PATCH] KVM: vmx, svm: always run with EFER.NXE=1 when shadow paging is active
Date: Mon, 28 Oct 2019 04:02:20 -0400 [thread overview]
Message-ID: <20191028080220.GH1560@sasha-vm> (raw)
In-Reply-To: <b08a0103-312e-5441-9ffe-33c9df0a9d57@redhat.com>
On Mon, Oct 28, 2019 at 08:56:26AM +0100, Paolo Bonzini wrote:
>On 28/10/19 07:59, Sasha Levin wrote:
>>
>> This commit has been processed because it contains a -stable tag.
>> The stable tag indicates that it's relevant for the following trees: all
>>
>> The bot has tested the following trees: v5.3.7, v4.19.80, v4.14.150, v4.9.197, v4.4.197.
>>
>> v5.3.7: Build OK!
>> v4.19.80: Failed to apply! Possible dependencies:
>> Unable to calculate
>>
>> v4.14.150: Failed to apply! Possible dependencies:
>> Unable to calculate
>>
>> v4.9.197: Failed to apply! Possible dependencies:
>> Unable to calculate
>>
>> v4.4.197: Failed to apply! Possible dependencies:
>> Unable to calculate
>>
>>
>> NOTE: The patch will not be queued to stable trees until it is upstream.
>>
>> How should we proceed with this patch?
>
>It should apply just fine to all branches, just to arch/x86/kvm/vmx.c
>instead of arch/x86/kvm/vmx/vmx.c.
I wonder if we should be carrying symlinks in the stable branches to
make this smoother...
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-10-28 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 15:23 [PATCH] KVM: vmx, svm: always run with EFER.NXE=1 when shadow paging is active Paolo Bonzini
2019-10-28 6:59 ` Sasha Levin
2019-10-28 7:56 ` Paolo Bonzini
2019-10-28 8:02 ` Sasha Levin [this message]
2019-10-29 9:32 ` Joerg Roedel
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=20191028080220.GH1560@sasha-vm \
--to=sashal@kernel.org \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).