From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Heiko Carstens <hca@linux•ibm.com>,
Vasily Gorbik <gor@linux•ibm.com>,
Christian Borntraeger <borntraeger@de•ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
"Mike Rapoport (Microsoft)" <rppt@kernel•org>
Subject: Re: linux-next: manual merge of the s390 tree with the mm tree
Date: Wed, 20 Nov 2024 12:19:08 +1100 [thread overview]
Message-ID: <20241120121908.15749360@canb.auug.org.au> (raw)
In-Reply-To: <20241028111606.5c009055@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2650 bytes --]
Hi all,
On Mon, 28 Oct 2024 11:16:06 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Today's linux-next merge of the s390 tree got conflicts in:
>
> arch/s390/include/asm/set_memory.h
> arch/s390/mm/pageattr.c
>
> between commit:
>
> 4c5768ef0fd7 ("arch: introduce set_direct_map_valid_noflush()")
>
> from the mm-unstable branch of the mm tree and commit:
>
> 2835f8bf5530 ("s390/pageattr: Implement missing kernel_page_present()")
>
> from the s390 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.
>
>
> diff --cc arch/s390/include/asm/set_memory.h
> index 240bcfbdcdce,cb4cc0f59012..000000000000
> --- a/arch/s390/include/asm/set_memory.h
> +++ b/arch/s390/include/asm/set_memory.h
> @@@ -62,6 -62,6 +62,7 @@@ __SET_MEMORY_FUNC(set_memory_4k, SET_ME
>
> int set_direct_map_invalid_noflush(struct page *page);
> int set_direct_map_default_noflush(struct page *page);
> +int set_direct_map_valid_noflush(struct page *page, unsigned nr, bool valid);
> + bool kernel_page_present(struct page *page);
>
> #endif
> diff --cc arch/s390/mm/pageattr.c
> index 4c7ee74aa130,aec9eb16b6f7..000000000000
> --- a/arch/s390/mm/pageattr.c
> +++ b/arch/s390/mm/pageattr.c
> @@@ -406,17 -406,21 +406,33 @@@ int set_direct_map_default_noflush(stru
> return __set_memory((unsigned long)page_to_virt(page), 1, SET_MEMORY_DEF);
> }
>
> +int set_direct_map_valid_noflush(struct page *page, unsigned nr, bool valid)
> +{
> + unsigned long flags;
> +
> + if (valid)
> + flags = SET_MEMORY_DEF;
> + else
> + flags = SET_MEMORY_INV;
> +
> + return __set_memory((unsigned long)page_to_virt(page), nr, flags);
> +}
> ++
> + bool kernel_page_present(struct page *page)
> + {
> + unsigned long addr;
> + unsigned int cc;
> +
> + addr = (unsigned long)page_address(page);
> + asm volatile(
> + " lra %[addr],0(%[addr])\n"
> + " ipm %[cc]\n"
> + : [cc] "=d" (cc), [addr] "+a" (addr)
> + :
> + : "cc");
> + return (cc >> 28) == 0;
> + }
> +
> #if defined(CONFIG_DEBUG_PAGEALLOC) || defined(CONFIG_KFENCE)
>
> static void ipte_range(pte_t *pte, unsigned long address, int nr)
This is now a conflict between the mm-stable tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-11-20 1:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 0:16 linux-next: manual merge of the s390 tree with the mm tree Stephen Rothwell
2024-11-20 1:19 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-12 1:07 Stephen Rothwell
2025-03-30 23:24 ` Stephen Rothwell
2023-07-30 23:37 Stephen Rothwell
2023-07-24 23:40 Stephen Rothwell
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=20241120121908.15749360@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=borntraeger@de$(echo .)ibm.com \
--cc=gor@linux$(echo .)ibm.com \
--cc=hca@linux$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rppt@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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