From: Borislav Petkov <bp@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Wei Liu <wei.liu@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Tianyu Lan <Tianyu.Lan@microsoft.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: linux-next: manual merge of the hyperv tree with the tip tree
Date: Tue, 26 Oct 2021 10:27:26 +0200 [thread overview]
Message-ID: <YXe77nC1uNKiuPch@zn.tnic> (raw)
In-Reply-To: <20211026172251.0f655709@canb.auug.org.au>
On Tue, Oct 26, 2021 at 05:22:51PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the hyperv tree got a conflict in:
>
> arch/x86/mm/pat/set_memory.c
>
> between commit:
>
> e9d1d2bb75b2 ("treewide: Replace the use of mem_encrypt_active() with cc_platform_has()")
>
> from the tip tree and commit:
>
> cf90c4532b92 ("x86/hyperv: Add new hvcall guest address host visibility support")
>
> from the hyperv tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc arch/x86/mm/pat/set_memory.c
> index 527957586f3c,525f682ab150..000000000000
> --- a/arch/x86/mm/pat/set_memory.c
> +++ b/arch/x86/mm/pat/set_memory.c
> @@@ -2024,6 -2025,17 +2026,17 @@@ static int __set_memory_enc_pgtable(uns
> return ret;
> }
>
> + static int __set_memory_enc_dec(unsigned long addr, int numpages, bool enc)
> + {
> + if (hv_is_isolation_supported())
> + return hv_set_mem_host_visibility(addr, numpages, !enc);
> +
> - if (mem_encrypt_active())
> ++ if (cc_platform_has(CC_ATTR_MEM_ENCRYPT))
> + return __set_memory_enc_pgtable(addr, numpages, enc);
> +
> + return 0;
> + }
> +
> int set_memory_encrypted(unsigned long addr, int numpages)
> {
> return __set_memory_enc_dec(addr, numpages, true);
Looks good, thanks.
Wei, you could mention this conflict when sending to Linus or you can
simply merge into your branch the tip branch tip:x86/cc which has the
cc_platform_has() changes and then redo the isolation VM stuff ontop.
HTH.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next prev parent reply other threads:[~2021-10-26 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 6:22 linux-next: manual merge of the hyperv tree with the tip tree Stephen Rothwell
2021-10-26 8:27 ` Borislav Petkov [this message]
2021-10-28 10:39 ` Wei Liu
-- strict thread matches above, loose matches on Subject: below --
2021-06-21 10:01 Stephen Rothwell
2021-03-15 3:35 Stephen Rothwell
2021-03-15 19:09 ` Michael Kelley
2021-03-16 15:02 ` Borislav Petkov
2021-03-16 15:05 ` Wei Liu
2021-03-16 21:07 ` Stephen Rothwell
2021-03-16 21:31 ` Borislav Petkov
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=YXe77nC1uNKiuPch@zn.tnic \
--to=bp@suse.de \
--cc=Tianyu.Lan@microsoft.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=wei.liu@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